Sending Bitcoin through a wallet looks straightforward. You enter the recipient’s address, choose an amount, review the details, and press Send. But the transaction doesn’t immediately become part of the blockchain.
Behind that simple action is a process involving digital signatures, network verification, transaction fees, and block confirmations. Understanding these steps helps explain why Bitcoin payments sometimes take longer than expected.
What Happens When You Send Bitcoin?
When you send Bitcoin, your wallet creates a transaction using funds available to spend.
Bitcoin follows a system called Unspent Transaction Outputs (UTXOs). These are outputs from previous transactions that have not yet been spent. Instead of treating your balance as a single number, your wallet selects suitable UTXOs to fund a new payment.
For example, suppose your wallet uses a UTXO worth 0.01000 BTC to send 0.00600 BTC.
The transaction could produce two outputs: 0.00600 BTC for the recipient and 0.00399 BTC returned to an address controlled by your wallet. The remaining 0.00001 BTC, or 1,000 satoshis, becomes the transaction fee.
These figures are illustrative, not current network fee estimates. Actual transactions may use several inputs and outputs, depending on the available UTXOs and the wallet’s settings.
How Digital Signatures Authorize Transactions
Before a transaction is broadcast, the wallet must provide the information required to authorize spending its selected inputs.
For common Bitcoin transactions, this involves creating digital signatures using the appropriate private keys.
The signatures allow network participants to verify that the transaction satisfies the relevant spending conditions without exposing those private keys.
A valid signature alone is not enough, however. Nodes must also check other rules, including whether the referenced outputs exist and remain unspent.
Once the transaction is properly constructed and signed, it can be submitted to the Bitcoin network.
Broadcasting Transactions and the Mempool
Bitcoin operates through a peer-to-peer network of computers called nodes.
When a wallet broadcasts a transaction, connected nodes can check it against Bitcoin’s consensus rules and their own transaction relay policies. Accepted transactions may then be forwarded to other nodes.
Unconfirmed transactions are commonly kept in a temporary collection called the mempool, short for memory pool.
There is no single global Bitcoin mempool. Each node maintains its own collection of unconfirmed transactions, so one node may have transactions that another has not received or accepted.
A transaction in the mempool has not yet been included in a confirmed block. It is waiting for a miner to select it.
Why Do Bitcoin Transaction Fees Vary?
Bitcoin transaction fees are not directly determined by how much BTC you send.
The main factors are the transaction’s virtual size and its fee rate, usually expressed in satoshis per virtual byte (sat/vB).
Transactions with multiple inputs often require more block space than simpler transactions. As a result, sending a small amount of Bitcoin can sometimes cost more than sending a larger amount.
Network demand also matters. When many transactions compete for limited block space, higher fee rates generally make transactions more attractive to miners.
Most wallets estimate suitable fees based on recent network conditions and a desired confirmation target. These estimates help users choose between cost and urgency, but they cannot guarantee an exact confirmation time.
From Mempool to Blockchain Confirmation
Miners assemble candidate blocks using transactions available to them. Transaction fees provide an incentive to include particular payments, although miners ultimately decide which valid transactions to select.
When a miner successfully produces a block meeting Bitcoin’s proof-of-work requirements, the block is broadcast to the network.
Full nodes independently verify the block before accepting it.
A transaction receives its first confirmation when it is included in a block on the accepted blockchain. Each additional block built on top of it increases the confirmation count.
More confirmations generally make reversing the transaction increasingly difficult. However, Bitcoin does not provide absolute, immediate transaction finality.
What If a Bitcoin Transaction Gets Stuck?
A Bitcoin transaction may remain unconfirmed when its fee rate is too low compared with other transactions competing for block space.
Some nodes may eventually remove an unconfirmed transaction from their mempools because of storage limits or local policies. This does not necessarily mean the transaction has disappeared from the entire network.
One possible solution is Replace-by-Fee (RBF). Supported wallets can create a replacement transaction that spends at least one of the same inputs while offering a higher fee.
Whether nodes accept the replacement depends on their mempool policies and the applicable fee requirements. A successful replacement can improve the chances of confirmation, but it still offers no guarantee.
If a transaction appears stuck, checking its status and fee rate is a sensible first step before attempting a replacement or another payment.
What Happens After You Press Send?
A Bitcoin payment involves more than transferring a number between two wallet balances.
The wallet constructs and authorizes a transaction, nodes verify and relay it, and miners compete to include it in a block. Once the block is accepted, the transaction begins accumulating confirmations.
The mempool and transaction fee market help explain what happens between sending a payment and seeing it confirmed.
Knowing how these stages fit together makes Bitcoin transactions easier to follow, particularly when a payment is pending or taking longer than expected.
References
- Antonopoulos, A. M., & Harding, D. A. (2023). Mastering Bitcoin: Programming the Open Blockchain (3rd ed.). O’Reilly Media. Chapter 6: Transactions, Chapter 8: Signatures, Chapter 9: Transaction Fees, and Chapter 10: Bitcoin Network.
- Bitcoin Developer Documentation. (n.d.). Bitcoin Developer Guides — Transactions. Technical Documentation.
- Bitcoin Developer Documentation. (n.d.). Bitcoin Developer Guides — P2P Network. Technical Documentation.
- Bitcoin Developer Documentation. (n.d.). Bitcoin Developer Guides — Block Chain. Technical Documentation.
- Bitcoin Optech. (n.d.). Fee Estimation. Technical Reference.
- Bitcoin Optech. (n.d.). Replace-by-Fee (RBF). Technical Reference.
- Bitcoin Core Developers. (n.d.). Mempool Replacements. Bitcoin Core Technical Documentation.
