
What Happens When You Send Bitcoin?
Follow a payment through signing, broadcast, validation, mining and confirmation.
You enter an address and amount, review a fee and tap Send. The wallet may immediately show a transaction ID, but your payment has only begun its journey. Creating a valid payment, sharing it with peers and getting it into a block are separate steps.
Let's follow an ordinary on-chain payment from Alice to Bob. This is a simplified self-custody example; an exchange withdrawal can add service processing, and a Lightning payment follows a different path.
The Payment Journey at a Glance
- Build + sign: Wallet prepares payment.
- Broadcast: Share with peers.
- Validate + mine: Check, select, include.
- Confirmations: Blocks build on top.
Figure 1. Nodes check transactions before relay and independently validate blocks after mining. These stages involve many participants.
1. The Wallet Constructs the Payment
Alice's wallet selects unspent transaction outputs (UTXOs) as inputs. It creates an output paying Bob and usually another returning change to Alice. The difference between total input value and total output value is the transaction fee. The selected outputs are consumed in full when spent. [1]
2. Signing Satisfies Spending Conditions
The wallet arranges the required signatures, possibly using a hardware device or multiple signers. These prove authorization under the inputs' spending conditions. Private signing keys remain with the signer; they are not sent to Bob or broadcast with the transaction. [1, 2]
Check Before Signing
Review the recipient, amount, fee and change using the wallet's transaction preview. A signature authorizes the transaction according to its signing rules; it does not mean the network has accepted or confirmed it.
3. The Signed Transaction Reaches Peers
A network-connected wallet component sends the transaction to a node or a service that relays it. Peers can announce it to other peers, which request and check transactions they do not already know. Bob does not need to be online to receive an ordinary on-chain payment. [2, 3]
4. Nodes Check Rules Before Relaying
| Check | What it is trying to establish |
|---|---|
| Inputs and value | Referenced outputs can be spent in the relevant chain or mempool view, with no invalid value creation. |
| Spending conditions | The signatures and scripts satisfy the rules for those inputs. |
| Conflicts and restrictions | The transaction does not violate applicable spending, timing or other consensus requirements. |
| Local relay policy | The node is willing to admit and relay it under its own fee, resource and policy rules. |
Consensus rules govern what a valid block may contain. Relay and mempool policies govern which unconfirmed transactions a node accepts and forwards. A transaction can be consensus-valid yet fail a particular node's relay policy. Mining does not override consensus validity. [3, 9]
Mempools Are Local Views
- Node A: Its own accepted transactions.
- Node B: Its own accepted transactions.
- Miner / pool node: Candidates for a block.
Figure 2. Peers exchange transactions, but there is no single global mempool. Timing, connectivity and policy can produce different local views.
An accepted unconfirmed transaction can wait in a node's mempool. It can later be mined, replaced under policy, or removed. Seeing it in one explorer establishes that the service knows about it, not that every node has accepted it. [3, 7]
A TXID Is an Identifier, Not a Receipt of Settlement
A wallet can compute a transaction ID before successful broadcast. Check the actual network status; an ID or a local "sent" label alone does not establish block inclusion.
5. A Miner Assembles a Candidate Block
Mining software selects eligible transactions for a block template, respecting limits and transaction dependencies. Fees provide an incentive to include transactions, but the block is not simply a guaranteed first-in, first-out queue. Mining hardware repeatedly hashes candidate block headers, seeking a hash that meets the required target. [4]
A successful miner publishes the block. Full nodes verify its proof of work, transactions and other consensus requirements. They accept it only if it is valid under their rules. A miner cannot make an invalid spend acceptable merely by including it in a block. [4, 5]
6. Inclusion Gives the First Confirmation
If Alice's transaction appears in a block on the node's active valid chain, it has one confirmation. Each subsequent block built on that chain adds one. The recipient output and Alice's change become part of the confirmed UTXO state. [1, 5]
Counting Confirmations
- Block H - 1: Before the payment.
- Block H: Payment included.
- Block H + 1: 2 confirmations.
- Block H + 2: 3 confirmations.
Figure 3. Block H gives the first confirmation. At tip H + 2, the payment has three confirmations: (H + 2) - H + 1 = 3.
Why Additional Blocks Matter
Nodes follow the valid chain with the greatest cumulative proof of work. Competing blocks can cause a reorganization, changing which recent transactions are confirmed. More confirmations generally make reversal harder; they do not provide an absolute mathematical guarantee that history can never change. [6, 9]
Bitcoin targets roughly ten minutes between blocks on average. Individual intervals vary, and a transaction may wait through several blocks before inclusion. Ten minutes is neither an exact countdown nor a promise that your payment will confirm in the next block. [6]
Choose a Receiving Policy for the Situation
A recipient or service decides how many confirmations to require based on its risk and operational needs. A payment can be visible on-chain before the receiving service credits the account.
What Your Wallet Is Telling You
| Status | What it means to check |
|---|---|
| Created or signed | The transaction exists locally; broadcast may not have succeeded. |
| Unconfirmed / pending | A service or node knows about it, but it has no active-chain confirmation yet. |
| Confirmed | It is included in the active chain; inspect the confirmation count and recipient output. |
| Missing or conflicted | It may be unknown, removed, replaced or conflicting. Check details before assuming the outcome. |
Why a Payment May Take Longer
Block space is limited, transactions compete and peer policies differ. A low fee rate, transaction dependencies or delayed broadcast can all affect progress. A higher fee can improve incentives for inclusion, but it cannot fix invalid signatures or guarantee a deadline. [3, 4]
Replace-by-fee (RBF) creates a higher-fee replacement spending overlapping inputs. Child-pays-for-parent (CPFP) spends an unconfirmed output with a fee that encourages mining both transactions. Availability depends on the wallet, outputs and node policies. [7, 8]
Inspect One Transaction Without Moving Funds
Compare the transaction ID, recipient output, fee and confirmations in your wallet or an explorer. Follow any replacement transaction too. Distinguish blockchain status from a receiving service's decision to credit an account.
The Journey to Remember
The wallet builds and signs. Peers relay and validate. A miner proposes a block, and full nodes verify it. Inclusion starts the confirmation count; later blocks strengthen confidence in that payment's place in the chain.
Sources & Further Reading
- Bitcoin Developer Guide. Transactions.
- Bitcoin Developer Guide. Wallets.
- Bitcoin Developer Guide. P2P Network.
- Bitcoin Developer Guide. Mining.
- Bitcoin Developer Guide. Block Chain.
- Bitcoin.org. Some things you need to know.
- Bitcoin Optech. Replace-by-fee.
- Bitcoin Optech. Child pays for parent.
- Nakamoto (2008). Bitcoin: A Peer-to-Peer Electronic Cash System.
Diagrams simplify an on-chain payment. Policies vary by software and release. Sources checked 2 November 2026.
Contact Tecneural Software Solutions
🌐 Website: Tecneural Software Solutions
📧 Email: support@tecneural.com
📞 Contact: +91 96555 17034


