Sending Bitcoin, Understanding Fees, and the Mempool
The Concept
When you hit "send" on a Bitcoin transaction, it doesn't travel directly to the recipient. It broadcasts out across the peer-to-peer network and lands in the mempool — short for "memory pool," the shared waiting room of transactions that have been announced but not yet included in a block. Every node on the network keeps its own version of this waiting room, and every miner picks from it when assembling the next block.
Block space is scarce: a Bitcoin block has a fixed capacity (roughly limited by the block weight, around 1–4 MB depending on transaction types), and new blocks arrive on average every 10 minutes. When more transactions are waiting than can fit in the next block, miners don't pick randomly — they prioritize by fee rate, measured in satoshis per virtual byte (sat/vB). A transaction offering a higher fee rate is more profitable for the miner to include, so it jumps the queue. This makes the fee market exactly that: a market. It is not a fixed service charge set by a company; it is a real-time auction for limited space, and the "right" fee depends entirely on how congested the mempool is at the moment you send.
It's worth separating two numbers that are easy to confuse: the total fee (in dollars or satoshis) and the fee rate (sat/vB). A larger transaction — one spending many small inputs, for example — takes up more bytes of block space even at the same fee rate, so it pays a higher total fee for the same priority level. Wallets typically show you the fee rate and let you choose a speed tier, but the actual dollar cost depends on your transaction's size, not just the rate you pick. This is why consolidating many small UTXOs (unspent transaction outputs) into fewer, larger ones during quiet, low-fee periods is a common cost-saving habit among frequent Bitcoin users.
Worked Example
Picture two contrasting moments:
Quiet period: The mempool holds only a few thousand pending transactions, well under what the next several blocks can absorb. Even a transaction with a low fee rate (say, 2 sat/vB) gets swept into the very next block, because there's no competition for space — miners will include almost anything that pays something rather than leave block space empty.
Busy period: A sudden surge of activity (a popular NFT mint, a market crash triggering mass withdrawals, a new protocol launch) floods the mempool with tens of thousands of pending transactions — far more than the next dozen blocks can hold. Now a 2 sat/vB transaction sits at the back of a very long line. Transactions offering 50+ sat/vB confirm quickly; the low-fee transaction might wait many blocks, translating to hours, before enough higher-paying transactions clear out of the way.
The visual way to think about this: imagine the mempool size charted over time as a rising and falling line. When the line is low, almost any fee confirms fast. When the line spikes, only the top of the fee-rate stack gets through each block, and everyone below waits their turn. Most wallets and block-explorer sites publish a live mempool chart and recommended fee tiers pulled from exactly this data, so you rarely have to guess — you can check current conditions before sending.
Exercise
You're sending the same amount of Bitcoin in two different scenarios, and your wallet offers three fee-rate options: Low (5 sat/vB), Medium (20 sat/vB), and High (60 sat/vB). For each scenario, pick a fee rate and explain the tradeoff in one or two sentences:
- You need the transaction confirmed in the very next block — it's time-sensitive (e.g., meeting an exchange withdrawal deadline).
- The transaction isn't urgent at all — you're moving funds to cold storage and are fine waiting up to a day.
Answer key for self-check: For scenario 1, choose High — paying a premium fee rate is the only reliable way to guarantee inclusion in the very next block regardless of current mempool congestion, since you're outbidding most competing transactions. For scenario 2, choose Low — since there's no time pressure, you can let the transaction wait in the mempool until congestion eases and it naturally gets picked up, saving on fees with no real cost other than patience. Medium would be a reasonable middle ground if you wanted "probably within a few blocks" without paying the premium or facing a long wait.
Recap
- Transactions wait in the mempool until a miner includes them in a block; block space is limited and allocated by fee rate, not by order received.
- Fees are a real-time market for scarce space — the "correct" fee depends on current congestion, your transaction's size in bytes, and how urgently you need confirmation.
- Understanding this prevents both overpaying during quiet periods and getting stuck during busy ones; next, we look at what a confirmation actually buys you in terms of finality.