> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/id/aplikasi-di-rome/via.md).

# Via Explorer

Via — penjelajah blok lintas-VM untuk chain Rome.

Via adalah penjelajah blok milik Rome, dibangun untuk model lintas-VM. Di samping blok, transaksi, token, dan alamat yang biasa, Via menghubungkan setiap transaksi EVM ke **Transaksi Solana** yang menyelesaikannya, dan menampilkan program serta instruksi Solana di balik panggilan melalui precompile CPI.

Karena transaksi EVM Rome dieksekusi di dalam program Solana, "apa yang sebenarnya terjadi di Solana" adalah bagian yang tidak bisa ditampilkan oleh penjelajah EVM biasa. Via bisa.

## Instans

Via berjalan per chain:

* Hadrian (testnet): [via-hadrian.testnet.romeprotocol.xyz](https://via-hadrian.testnet.romeprotocol.xyz/)

## Apa yang perlu dicari

Buka transaksi apa pun dan ikuti tautan "Settled in" ke transaksi Solana yang menyelesaikannya; penjelajah Solana menampilkan instruksi dan compute unit transaksi tersebut. Panggilan melalui precompile CPI juga menampilkan program dan instruksi Solana yang mereka panggil, dan satu batch panggilan menampilkan CPI dari setiap sub-panggilan. Baca compute unit dari transaksi Solana, karena EVM `gasUsed` bukanlah proksi yang akurat untuk compute Solana di Rome.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rome.builders/id/aplikasi-di-rome/via.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
