> 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/how-can-i-send-an-on-chain-transaction-with-blink.md).

# How can I send an on-chain transaction with Blink?

To send an on-chain transaction with Blink, please follow these steps:

1. Open the Blink app and click on the `Send` button.
2. Enter the recipient's Bitcoin on-chain address or scan their QR code.
3. Choose if you want to spend from your Bitcoin Balance or Dollar Balance.
4. Input the amount you want to send and an optional note for yourself.
5. Tap `Next` and double check the details.
6. Move the slider to the right to complete the transaction.
7. Once the transaction is confirmed, you can share the transaction ID (also known as the `hash` or `txid`) with the recipient as a proof of the successful transaction.

If the mining fees calculated are more than the 10% of the amount you are preparing to send Blink will show a notification: `High fee! We recommend Lightning.`

Note that on-chain transactions may take some time to confirm on the Bitcoin network, depending on the current network traffic and the transaction fees chosen.


---

# 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/how-can-i-send-an-on-chain-transaction-with-blink.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.