> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/blink-payment-methods/on-chain/where-can-i-verify-the-status-of-an-on-chain-transaction.md).

# Where can I verify the status of an on-chain transaction?

You can verify the status of an on-chain transaction by using a blockchain explorer like [mempool.com](https://mempool.com). A blockchain explorer is a tool that allows you to search and view all the transactions that have occurred on the Bitcoin blockchain.

To check the status of your transaction, you will need the transaction ID or hash. This information can usually be found in your wallet transaction history or on the transaction confirmation page.

Once you have the transaction ID or hash, you can enter it into a blockchain explorer search bar, and it will show you the details of the transaction, including the number of confirmations and the current status.


---

# 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://faq.blink.sv/blink-payment-methods/on-chain/where-can-i-verify-the-status-of-an-on-chain-transaction.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.