> 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/zh/rome-shang-de-ying-yong/via.md).

# 通过 Explorer

Via——用于 Rome 链的跨 VM 区块浏览器。

Via 是 Rome 的区块浏览器，专为跨 VM 模型构建。除了常见的区块、交易、代币和地址之外，它还会将每笔 EVM 交易关联到 **Solana 交易** 完成结算它的 Solana 交易，并显示通过 CPI 预编译合约发起调用背后的 Solana 程序和指令。

由于 Rome 的 EVM 交易是在 Solana 程序内执行的，“Solana 上实际发生了什么”是普通 EVM 浏览器无法展示的部分。Via 可以。

## 实例

Via 按链运行：

* Hadrian（测试网）： [via-hadrian.testnet.romeprotocol.xyz](https://via-hadrian.testnet.romeprotocol.xyz/)

## 应关注的内容

打开任意交易并跟随其“Settled in”链接，查看完成该交易结算的 Solana 交易；Solana 浏览器会显示该交易的指令和计算单元。通过 CPI 预编译合约发起的调用也会显示其调用的 Solana 程序和指令，而一批调用则会显示每个子调用的 CPI。请从 Solana 交易中读取计算单元，因为 EVM `gasUsed` 并不能真实反映 Rome 上的 Solana 计算量。


---

# 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/zh/rome-shang-de-ying-yong/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.
