> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/wiki/standards-protocols-and-tools/building-on-bitcoin/block-explorer.md). # Block Explorer A **block explorer** is a web-based or software tool that allows users to browse the Bitcoin blockchain, searching and viewing details of blocks, transactions, and addresses. Block explorers query a node's copy of the ledger (or an indexed database built from it) and present the data in a human-readable form, typically showing block height, block hash, timestamp, included transactions, and the inputs/outputs and value transferred by each transaction. Block explorers are commonly used by developers to debug and verify transactions, by users to confirm that a payment has been included in a block, and by businesses to audit on-chain activity. Examples for the BSV network include [WhatsOnChain](https://whatsonchain.com/). --- # 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://hub.bsvblockchain.org/wiki/standards-protocols-and-tools/building-on-bitcoin/block-explorer.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.