> 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/es/apps-en-rome/via.md).

# Via Explorer

Via — el explorador de bloques entre VM para las cadenas de Rome.

Via es el explorador de bloques de Rome, construido para el modelo entre VMs. Junto con los bloques, transacciones, tokens y direcciones habituales, muestra el **lado de Solana** de cada transacción EVM — el programa e instrucción exactos de Solana a los que se resolvió cada llamada.

Como una transacción EVM de Rome se ejecuta dentro de un programa de Solana, "lo que realmente ocurrió en Solana" es la parte que un explorador EVM normal no puede mostrar. Via sí puede.

## Instancias

Via se ejecuta por cadena:

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

## Qué buscar

Abre cualquier transacción y lee las instrucciones de Solana detrás de ella — llamadas CPI a SPL Token, Meteora o cualquier programa de Solana, además de las unidades de cómputo consumidas. Esta es la forma fiable de ver el costo real de Solana (EVM `gasUsed` no es un sustituto fiel de las unidades de cómputo de Solana en 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/es/apps-en-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.