> For the complete documentation index, see [llms.txt](https://svpchain.gitbook.io/svpchain-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://svpchain.gitbook.io/svpchain-docs/ecosystem/explorers.md).

# Explorers

Block explorers for SVPChain.

The official explorer is a [Blockscout](https://www.blockscout.com/) fork. The same URL serves both mainnet and testnet — switch networks via the in-app selector.

<table data-view="cards"><thead><tr><th>Explorer</th><th>URL</th></tr></thead><tbody><tr><td>SVPChain Explorer</td><td><a href="https://explorer.svpchain.com">explorer.svpchain.com</a></td></tr></tbody></table>

### What you can do

* Search by **transaction hash**, **address**, **block number**, or **block hash**.
* View token transfers, contract source (when verified), and read/write ABI.
* Verify and publish Solidity source for a deployed contract.
* Pull data via the Blockscout REST and GraphQL APIs (handy for quick analytics; not authoritative — verify against [JSON-RPC](/svpchain-docs/build/json-rpc.md) for production).

### Deep links

| Resource    | URL pattern                                    |
| ----------- | ---------------------------------------------- |
| Transaction | `https://explorer.svpchain.com/tx/<hash>`      |
| Address     | `https://explorer.svpchain.com/address/<addr>` |
| Block       | `https://explorer.svpchain.com/block/<number>` |
| Token       | `https://explorer.svpchain.com/token/<addr>`   |

### Verify a contract

From the contract's address page → **Code → Verify & Publish** → pick a flow (single file / multi-part / standard JSON input). Match the compiler version and optimizer settings used at deploy time exactly — the tiniest mismatch fails verification.

{% hint style="info" %}
The same explorer URL serves both networks. If a tx hash is "not found", make sure the network selector is set to the right one (testnet `2517` vs mainnet `2518`).
{% endhint %}

### Next steps

<table data-view="cards"><thead><tr><th>Related</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Endpoints reference</td><td><a href="/svpchain-docs/chain/networks.md">Networks</a></td></tr><tr><td>Deploy and verify a contract</td><td><a href="/svpchain-docs/build/deploy-a-contract.md">Deploy a contract</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://svpchain.gitbook.io/svpchain-docs/ecosystem/explorers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.