• Why Your Bitcoin Transaction Is Still Unconfirmed: The Mempool Explained
  • The Mempool Isn’t One Thing
  • How Miners Choose
  • Why Fees Spike
  • The RBF Escape Hatch
  • The Child-Pays-For-Parent Option
  • Key Takeaways

§Why Your Bitcoin Transaction Is Still Unconfirmed: The Mempool Explained

Every Bitcoin user eventually faces the frustrating moment: you sent a transaction, it’s been 3 hours, and it’s still “unconfirmed.” Understanding what happened reveals both how Bitcoin’s fee market works and how to avoid it next time.

§The Mempool Isn’t One Thing

Here’s the fundamental confusion: there is no single Bitcoin mempool. Every full node has its own mempool — a collection of unconfirmed transactions that node has received and validated. Different nodes have slightly different mempools depending on when they received transactions and how much memory they allocate to mempool storage.

When you check a block explorer and see your transaction “in the mempool,” you’re seeing one particular explorer’s node’s mempool. Your transaction might be in a different state on other nodes.

§How Miners Choose

Miners want to maximize fee revenue per block. Each block can fit approximately 4MB of transaction data. Given a mempool full of transactions, rational miners pick the highest-fee ones first.

The fee is measured in satoshis per virtual byte (sat/vB). A standard single-input, two-output transaction is about 225 vB. At 10 sat/vB, that’s 2,250 sats (roughly .50 at 7K). That’s the going rate for a confirmation within the next few blocks.

§Why Fees Spike

When activity surges — price moves, ETF flows, on-chain congestion — the mempool fills with pending transactions. Fee rates jump as users bid up block space. Transactions that were paying competitive rates an hour ago suddenly become underpriced.

This is fee estimation: if you’re using a wallet that estimates fees dynamically, you’re usually okay. If you’re using a wallet with a fixed fee setting from 6 months ago, you might be significantly underpriced.

§The RBF Escape Hatch

If your transaction is stuck, Replace-by-Fee (RBF) lets you broadcast a replacement transaction that pays the same inputs to the same outputs but with a higher fee. Miners prefer higher-fee transactions, so they’ll drop your original and pick up the replacement.

Not all wallets support RBF. Wallets that do will show “bump fee” as an option. This is generally the best solution for stuck transactions.

§The Child-Pays-For-Parent Option

If your stuck transaction has an output going to an address you control (change), you can do a Child-Pays-For-Parent (CPFP): spend the change output with a very high fee. Miners will include both transactions because the high fee on the child makes the whole family worth including.

This is more expensive but works when RBF isn’t available.

§Key Takeaways

• Mempools are per-node — your transaction state varies across explorers
• Miners pick highest-fee transactions first — fee market is auction-based
• Fee spikes happen during on-chain congestion from price moves or high activity
• RBF is the cleanest solution for stuck transactions (bump the fee)
• CPFP (child pays for parent) works when you control a change output
• Dynamic fee estimation in wallets prevents most stuck transaction problems

⚡ If this was useful, a zap is always welcome. tomford@rizful.com