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

# MayaScan

Maya Protocol's Blockchain Explorer

[**MayaScan**](https://www.mayascan.org/) is the main blockchain explorer offered by Maya Protocol, offering an extensive range of services for users to track their transactions, swaps, liquidity, network status, nodes and more.

**By entering** any of the supported MAYAChain addresses (Bitcoin, Ethereum, THORChain, Dash, Kujira, and of course MAYAChain) into the search field, users can easily view all the relevant information regarding the address.

**MayaScan** provides a secure platform for on-chain p2p messaging, allowing for anonymous communications between nodes.

As if this wasn’t enough, MayaScan also uses cutting-edge Ordinals technology and Memos to create and trade Native MAYAChain Tokens and Non-Fungible Tokens (NFTs).


---

# 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.mayaprotocol.com/blockchain-explorer/mayascan.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.