> For the complete documentation index, see [llms.txt](https://docs.doschain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doschain.com/ecosystem/doscan.md). # DOScan DOS Chain Block Explorer ## DOScan.io Our self-hosted explorer [doscan.io](https://doscan.io) offers a suite of powerful tools designed to help you track transactions, analyze DOS usage statistics, and access detailed information about validators. * Search using address, transaction hash, or block ID * Delve into detailed transaction information * Access, verify, and interact with smart contract source codes A Beam Testnet Explorer is also available: [test.doscan.io](https://test.doscan.io/). ## Snowtrace.io Access the Snowtrace Explorer for DOS at [7979.snowtrace.io](https://7979.snowtrace.io/), which offers tools for enhanced blockchain interaction: * View transactions, statistics, and validator details * Search using an address, transaction hash, or block ID * Explore details about ERC20, ERC721, and ERC1155 tokens * Delve into detailed transaction information * Access, verify, and interact with smart contract source codes --- # 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.doschain.com/ecosystem/doscan.md?ask=&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.