You press Send, a spinner spins, and somewhere value moves between strangers on the internet with no bank in between. The mechanics behind that spinner are worth knowing — not for trivia, but because every confusing thing about crypto (fees, delays, "the transaction is stuck", irreversible mistakes) becomes obvious once you can see the pipeline. Let's follow one transaction all the way through.
Step 1: Your wallet constructs and signs a message#
A blockchain transaction is, at bottom, a signed message: from this address, to that address, this much, optionally some instructions, at this fee level. The wallet builds it locally, then signs it with your private key using asymmetric cryptography — producing proof that the owner of that key authorized exactly this message, without revealing the key itself.
This is why wallets obsess over seed phrases. The private key isn't stored on any network; it exists only where you keep it. There are no password resets on blockchains — signature or silence. (And it's why "signing" arbitrary messages from websites deserves the same care as sending: a valid signature authorizes whatever it covers.)
Crucially, nothing has happened yet. The signed message exists only on your device.
Step 2: Broadcast — your transaction joins the mempool#
The wallet flings the signed transaction to one or more nodes in the peer-to-peer network. Valid transactions get relayed node-to-node and collect in each node's mempool — a waiting room of pending transactions replicated across thousands of machines worldwide.
In the mempool, fee markets come alive. Blocks hold limited space/compute (gas on Ethereum-style chains), so builders include transactions by profitability. Your fee bid — set manually or auto-estimated by the wallet — decides roughly how long you wait. Bid too low during congestion and you sit in the waiting room while pricier traffic jumps the queue; depending on chain rules you may eventually be dropped entirely rather than confirmed late.
That spinner in your wallet? It's watching the mempool.
Step 3: Inclusion — a validator proposes a block#
Every ~12 seconds on Ethereum-class chains (roughly every 10 minutes on Bitcoin), a participant earns the right to propose the next block:
- On proof-of-stake networks, validators stake capital as collateral; the protocol selects proposers and attesters, slashing stakes for provable misbehavior.
- On proof-of-work networks, miners expend electricity racing a puzzle; the winner appends the block and claims the reward.
The proposer pulls profitable mempool transactions, checks each signature and balance itself (nobody trusts anybody here — every full node re-verifies everything), executes them in order against its copy of world state, and publishes the resulting block. Your transaction now has one confirmation — included, but young.
Step 4: Finality — when "included" becomes "permanent"#
Here's the part newcomers underestimate. One confirmation means probably real; finality means practically irreversible:
- Other validators must attest to the block; their attestations stack into economic certainty.
- Reorganizations — a competing chain briefly winning — can displace young blocks, which is why exchanges wait for N confirmations before crediting deposits.
- On modern proof-of-stake chains, after two epochs (~13 minutes on Ethereum) the chain reaches finality: reversing the block would require destroying tens of millions of dollars' worth of staked collateral. At that point "immutable" stops being marketing.
For small purchases you'll act on one confirmation; for large transfers or exchange deposits, finality is the standard you actually care about.
Why transactions fail — and what fees buy#
Common failure modes map cleanly onto the pipeline:
- Stuck forever: fee bid below market during congestion; eventually evicted from the mempool. Nothing was lost except time — failed broadcasts never moved funds.
- Reverted after inclusion: smart-contract executions can fail mid-block (insufficient allowance, a slippage guard tripped). You paid for the computation that ran and failed; state rolled back cleanly.
- Wrong address: finality's dark side. No support desk exists downstream of a correct signature to an incorrect destination.
Fees, then, pay for two things: priority in line, and compensation for the decentralized computer work executed on your behalf — not a toll to some company, but the incentive layer keeping independent operators honest.
The takeaway#
A blockchain transaction is a signed message, relayed through gossip, auctioned into blocks, verified by everyone, and hardened into history by economic weight — no step of which requires trusting any single party. Once you can trace those five stages, every wallet warning, fee estimate, and confirmation counter stops being superstition and becomes just the pipeline, visible.
Related: security fundamentals cover the private-key hygiene side of this story, and self-hosting economics contrasts centralized infrastructure with the decentralized alternative.
