How long a Bitcoin treasury transfer takes

A Bitcoin treasury transfer can take minutes to approve and broadcast, around 10 minutes on average to receive its first confirmation, or longer if fees are too low or the receiving policy requires more confirmations. The clock has several parts: internal authorization, transaction construction, network relay, miner selection and the recipient’s settlement rule.

What happens between approval and confirmation?

A treasury team first authorizes the payment under its own controls. A custody system or wallet then selects spendable bitcoin outputs, builds a transaction with the recipient’s address and any change, and assigns a fee rate. Signers approve it, and the wallet broadcasts it to Bitcoin nodes. Those nodes check that it follows the network’s rules and relay it to miners.

Broadcast is not confirmation. Until a miner includes the transaction in a block, it has zero confirmations: a recipient may see it as pending, but it is not yet recorded in the blockchain. A move involving a different chain adds a separate bridge process; the rango bridge explainer covers how that path works.

The transaction fee affects its position in miners’ queues. The fee rate is measured against the transaction’s data size, and miners generally favor transactions offering more fee per unit of block space. A higher rate can improve the chance of prompt inclusion when demand is high. It cannot make a block arrive on schedule.

How long does each confirmation take?

Bitcoin blocks arrive about every 10 minutes on average. When a block containing the transaction is added to the chain, it gets its first confirmation. Each later block built on top adds another. The average time is not a timer: a block can arrive quickly, or the wait can run much longer.

As a rough planning estimate, one confirmation averages about 10 minutes from broadcast when the fee is competitive; three average about 30 minutes, and six about an hour. These are averages, not deadlines. If the transaction waits in the mempool before inclusion, that wait adds to the total. A treasury dashboard should therefore show approval, broadcast and confirmation as separate stages.

What determines when the transfer is complete?

The sender and recipient decide what “complete” means for their process. A company may treat the transfer as received once it sees a confirmation. A custodian, exchange or accounting policy may wait for several confirmations before crediting or reusing the funds. More confirmations make a reversal through a competing chain increasingly difficult, but they also extend settlement time.

For an ordinary treasury movement between addresses the same organization controls, the practical threshold may differ from a payment to an external counterparty. The receiving system’s rules govern when it makes the funds available; the transaction itself does not carry a universal completion time. Ask the recipient how many confirmations it requires before scheduling a payment against a deadline.

• Approval time depends on the organization’s signers and controls.
• Broadcast is usually quick after signing, but it is not on-chain confirmation.
• Fee rate and demand for block space influence how soon a miner includes the transaction.
• The confirmation threshold determines when the recipient treats it as settled.

For planning, allow for both the organization’s authorization workflow and the recipient’s confirmation rule. A competitive fee makes prompt inclusion more likely, while extra confirmation requirements add roughly another 10 minutes each on average after the first block. Neither estimate guarantees a finish time.