How Crypto Transactions Actually Work
A step-by-step look at what happens between clicking "send" and a transaction being confirmed.
Jump to section
What to remember
- A transaction is signed with a private key, then broadcast to the network.
- It waits in a mempool until included in a block.
- Confirmations accumulate as more blocks are added afterward.
- "Sent" and "confirmed" are meaningfully different states.
Step 1: Creating and signing the transaction
Your wallet builds a transaction message (sender, recipient, amount, and a few technical fields) and signs it using your private key. This signature cryptographically proves the transaction was authorized by whoever controls that key, without ever exposing the key itself.
Step 2: Broadcasting to the network
The signed transaction is broadcast to the network and enters a waiting area of unconfirmed transactions, often called the mempool, where it waits to be picked up and included in an upcoming block.
Step 3: Validation and inclusion in a block
- Network participants (miners or validators, depending on the network) check that the transaction follows the rules — for example, confirming the sender actually has sufficient funds.
- A valid transaction is included in a new block, generally chosen with some preference for transactions offering a higher fee.
Step 4: Confirmation
Once a transaction's block is added to the chain, it has one confirmation. As more blocks are added on top of it, it gains additional confirmations, and the practical likelihood of it ever being reversed drops further with each one — which is why many services wait for multiple confirmations before treating a transaction as final.
The four steps between clicking send and a transaction being confirmed -- sign, broadcast, validate and include, confirm.
"Sent" and "confirmed" are not the same moment
A transaction can be broadcast successfully but still be waiting for confirmation. Treating a transaction as fully final the instant it's sent, before it has adequate confirmations, is a common and avoidable source of confusion.
What to remember
- A transaction is signed with a private key, then broadcast to the network.
- It waits in a mempool until included in a block.
- Confirmations accumulate as more blocks are added afterward.
- "Sent" and "confirmed" are meaningfully different states.