> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/develop/basics/use-a-block-explorer.md).

# Use a Block Explorer

Navigate Chiliz Chain's two block explorers, Chiliscan (Routescan) and Chiliz Block Explorer (Blockscout), for transactions, NFTs, address lookup, and contract verification.

A block explorer is an application used by every blockchain to allow users to view transactions being carried out on that blockchain. It can give an overview of other on-chain activities. It is comparable to a digital passbook.

Block explorers are also used to verify smart-contracts after they are deployed.

One blockchain may have more than one block explorer.

## Chiliz Chain Mainnet block explorers

Chiliz Chain has two block explorers for its Chiliz Mainnet, which you can use to see recent transactions.

You can also use them to view your own transactions and statuses, display your collected NFTs, look up other addresses, view transaction history, and verify your smart-contracts.

### **Chiliscan By Routescan**

{% embed url="<https://chiliscan.com>" %}

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2FlAxhZd1Oggqv0TzOXF54%2Fimage.png?alt=media&amp;token=a319f9ea-59f4-4971-8a15-8033b0c1b4a4" alt=""><figcaption></figcaption></figure>

### **Chiliz Chain Explorer by Blockscout**

{% embed url="<https://scan.chiliz.com/>" %}

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2FQj51O6Iosj3boxtwLkVO%2Fimage.png?alt=media&amp;token=fbc7d38e-e941-4bf4-9450-773d8428554c" alt=""><figcaption></figcaption></figure>

## Spicy Testnet block explorers

Chiliz Chain has two block explorers for its Spicy Testnet, which you can use to see recent transactions.

You can also use them to view your own transactions and statuses, display your collected NFTs from the Testnet, look up other addresses, view transaction history, and verify your smart-contracts.

### **Chiliscan By Routescan**

{% embed url="<https://testnet.chiliscan.com>" %}

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2FN7R69VgYEjyzdgcBKTDQ%2Fimage.png?alt=media&amp;token=915edc9a-2bf0-4665-9ba0-ed2be3a12be3" alt=""><figcaption></figcaption></figure>

### **Chiliz Chain Explorer by Blockscout**

{% embed url="<https://spicy-explorer.chiliz.com>" %}

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2FIzVtXOqBDV7GboaDL0lH%2Fimage.png?alt=media&amp;token=3619879a-bbad-4c7d-8385-d52324d93b95" alt=""><figcaption></figcaption></figure>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chiliz.com/develop/basics/use-a-block-explorer.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 `build a script that syncs our docs to a CMS` 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.