> 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/transaction-fees/what-are-the-fees-for-sending-bitcoin-from-my-blink-wallet-to-another-wallet.md).

# ¿Cuáles son las tarifas para enviar Bitcoin desde mi billetera Blink a otra billetera?

Las comisiones de transacción varían dependiendo del tipo de transacción, ya sea una transacción on-chain o una transacción Lightning.

Para enviar pagos Lightning, el usuario paga una comisión de enrutamiento, pero Blink no aplica comisiones adicionales.

Las comisiones de transacciones on-chain de Blink se componen de:

1. [**Comisión de minería**](/espanol/transaction-fees/what-are-mining-fees.md) — se paga según el estado actual de la mempool.
2. **Comisión fija escalonada** — varía según el monto del retiro. Consulta la App de Blink para los niveles actuales.
3. **Recargo por desbalance** — puede aplicarse una comisión adicional para cuentas que excedan el umbral de desbalance Lightning/on-chain en una ventana móvil.

El monto exacto de las comisiones de transacción puede variar dependiendo de las condiciones actuales del mercado y la congestión de la red. Consulta la App de Blink para las comisiones actuales.


---

# 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/transaction-fees/what-are-the-fees-for-sending-bitcoin-from-my-blink-wallet-to-another-wallet.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.