> 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/espanol/blink-payment-methods/on-chain/where-can-i-verify-the-status-of-an-on-chain-transaction.md).

# ¿Dónde puedo verificar el estado de una transacción on-chain?

Puede verificar el estado de una transacción on-chain utilizando un explorador de cadenas de bloques como [mempool.com](https://mempool.com). Un explorador de blockchain es una herramienta que permite buscar y ver todas las transacciones que se han producido en la blockchain de Bitcoin.

Para comprobar el estado de su transacción, necesitará el ID o hash de la transacción. Esta información suele encontrarse en el historial de transacciones de tu monedero o en la página de confirmación de la transacción.

Una vez que tengas el ID o hash de la transacción, puedes introducirlo en una barra de búsqueda del explorador de blockchain, y te mostrará los detalles de la transacción, incluido el número de confirmaciones y el estado actual.


---

# 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/espanol/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.