> 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/what-are-some-common-reasons-for-an-on-chain-transaction-to-take-a-long-time-to-confirm.md).

# What are some common reasons for an on-chain transaction to take a long time to confirm?

There are several reasons why an on-chain transaction may take longer than usual to confirm. Some common reasons include:

1. **Network congestion:** If there are many pending transactions on the Bitcoin network, miners may prioritize transactions with higher fees, leaving transactions with lower fees to wait longer.
2. **Low transaction fee:** If you set a low transaction fee, miners may not prioritize your transaction, leading to a longer confirmation time.

If your transaction is taking longer than expected, you can use a block explorer like mempool.com to check its status. If you are still experiencing issues, please contact our support team for assistance at <support@blink.sv>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faq.blink.sv/blink-payment-methods/on-chain/what-are-some-common-reasons-for-an-on-chain-transaction-to-take-a-long-time-to-confirm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.