Bitcoin Mempool Explained: Fees & Stuck Transactions
You sent bitcoin hours ago. The block explorer still says "unconfirmed," and you're starting to worry. Your bitcoin is not lost. It is waiting in line in the bitcoin mempool, the network's waiting room for transactions that haven't made it into a block yet.
The mempool (short for "memory pool") is the set of valid, unconfirmed transactions that each node holds until a miner includes them in a block. Every Bitcoin transaction passes through it. Most leave quickly. Some wait for hours or days, and the reason is almost always the fee rate they offered, not a fault in the network.
This guide explains how the waiting room works. It shows why fees depend on your transaction's size, not the amount you send, and how to rescue a transaction that is stuck right now. By the end, you'll be able to read a live mempool chart, choose your own fee, and stop overpaying.
π Stuck right now? Your funds are safe. Jump straight to Section 7: How to Fix a Stuck Bitcoin Transaction. It has a quick decision tree for senders and receivers.
π What You'll Learn
- What the Bitcoin mempool is, and why there is no single global mempool
- How fees are calculated: transaction size in vbytes Γ fee rate in sat/vB
- How to read a live mempool explorer such as mempool.space
- How to choose a fee based on how urgent your payment is
- How to fix a stuck transaction with RBF, CPFP, waiting, or an accelerator
β±οΈ Estimated Time: 25β30 minutes to read, plus about 10 minutes of hands-on practice with a live explorer
π Difficulty: BeginnerβIntermediate. Every acronym is defined the first time it appears.
πΊοΈ The 6-phase journey of every transaction: 1) Broadcast β 2) Mempool waiting room β 3) Fee-rate auction β 4) Miner selection β 5) Block confirmation β 6) Final settlement
Phase 6 note: Small payments are often treated as settled after one confirmation. Larger amounts usually wait for several. These are conventions set by each service, not protocol rules.
π§ Reading paths: Stuck senders, go to Section 7. Fee-shocked readers, go to Section 3. Curious learners, read from top to bottom.
Before You Start
To follow this guide, you'll need:
- Basic Bitcoin knowledge: what Bitcoin is, how wallets and addresses work, and how to send and receive. If you need a refresher, start with Bitcoin Origins and Mechanics Explained or Breaking Down Bitcoin: A Comprehensive Beginner-to-Expert Guide. Dedicated guides on wallets and address types are coming soon.
- Helpful but optional: UTXO basics. If "UTXO" is new to you, treat it as a single coin or bill in your wallet. The rest is explained along the way. A full guide on UTXOs and coin control is coming soon.
- A wallet that supports custom fee rates and RBF. Common examples are Sparrow (desktop, strong coin control), Electrum (desktop, RBF and CPFP built in), BlueWallet (mobile, fee bumping and cancel), and Bitcoin Core (full node software, open source under the MIT license, on GitHub).
- A public mempool explorer such as mempool.space. A second explorer, such as blockstream.info, is useful for cross-checking.
- Optional: your own node. Running one lets you see your own mempool instead of trusting a third party. A node-setup guide is coming soon.
β Mindset note: Nothing in this guide puts your funds at risk if you follow the steps. Looking up a transaction is read-only. Fee bumping only replaces your own transaction with a better-paying version.
1. What Is the Bitcoin Mempool?
The Bitcoin mempool is the set of valid, unconfirmed transactions a node holds in memory while they wait for a miner to include them in a block. Each node keeps its own mempool. Miners generally pick the transactions paying the highest fee rate first.
The Bitcoin developer documentation describes this ordering directly. Transactions "are prioritized based on their fee per byte, with higher-paying transactions being added in sequence until all of the available space is filled."
The Waiting Room Analogy
The mempool works like an airport standby lounge. Each flight is a block. Flights leave at a steady average pace, but the exact gaps between them vary. Every flight has a fixed number of seats, because each block has a maximum weight.
Passengers who pay the highest fare per seat board first. Low bidders keep waiting for a quieter flight. Nobody is kicked out of the airport for bidding low. They just wait longer.
There Is No Single Mempool
This is one of the most misunderstood parts of Bitcoin. There is no central, global queue. Thousands of nodes each keep a personal notebook of pending transactions. Transactions spread between nodes through peer-to-peer relay, often described as a "gossip" process.
These notebooks are usually very similar, but they are never identical. Nodes receive transactions at different times, run different settings, and may drop different transactions when full. This explains two common puzzles:
- Why explorers sometimes disagree. Each explorer shows the view from its own node or nodes.
- Why a transaction can vanish from one explorer but still appear on another. One node dropped it. Another kept it.
What Gets Into the Mempool (Validity, Standardness, Minimum Relay Fee)
A node checks every incoming transaction before accepting it. It applies three layers of rules:
- Validity (consensus rules): the signatures must be correct, the inputs must not already be spent, and the transaction can't create coins from nothing.
- Standardness (policy rules): node-level rules about script types, transaction size, and dust outputs. A transaction can be valid but still "non-standard," so most nodes won't relay it.
- Minimum relay fee: the lowest fee rate a node will accept and pass on to peers.
The minimum relay fee is a default that node operators can change, and that has changed across Bitcoin Core versions. Don't rely on an old number from a forum post. Check the release notes for the current version. At the time of writing, the latest Bitcoin Core release is v32.1.
How Long Transactions Can Stay (Memory Cap, Expiry, Eviction, Rebroadcasting)
Mempools are not infinite. Bitcoin Core gives each node a default memory cap (the maxmempool option) and a default expiry time for old transactions (the mempoolexpiry option). Operators can change both.
When a node's mempool fills up, it evicts the lowest-fee-rate transactions first. Its minimum entry fee then rises above the normal relay floor. When a transaction gets old enough, the node also expires it.
Expiry is not always the end of the story. Your wallet or other nodes may rebroadcast the transaction, so an "expired" transaction can reappear.
Being dropped from a mempool doesn't destroy your bitcoin. The coins never left your address, because the transaction never confirmed.
Now that the waiting room makes sense, the next step is to follow a single transaction from your wallet to the blockchain.
2. The Life of a Bitcoin Transaction (Step-by-Step)
Step 1 β Your Wallet Builds and Signs
Your wallet chooses one or more UTXOs as inputs. It then creates outputs, usually one for the recipient and one that returns your change. Finally, it signs the transaction with your private key. The Bitcoin developer documentation describes these signatures as using ECDSA on the secp256k1 curve.
The fee is never a separate line item. It is simply the leftover: total inputs minus total outputs. Whatever isn't assigned to an output goes to the miner.
Step 2 β Broadcast and Peer Relay
Your wallet sends the signed transaction to one or more nodes. Each node checks it against its own rules. If it passes, the node adds it to its mempool and relays it to its peers.
This spreading usually happens within seconds. Your transaction then appears on explorers as "unconfirmed."
Step 3 β Waiting in the Mempool
Your transaction now competes with every other pending transaction. It competes on fee rate (sat/vB), not on total fee. Back in the standby lounge, the fare per seat matters, not the total amount someone paid for extra luggage.
"Unconfirmed" means waiting, not failed.
Step 4 β A Miner Builds a Block Template
Miners sort pending transactions by fee rate. They also consider linked "packages," where a child transaction depends on an unconfirmed parent. They fill the block up to its weight limit, then compete to find a valid proof-of-work.
For more on how mining secures the chain, see Unpacking Bitcoin: Origins, Technology, and Impact Explained. For how proof-of-work compares with other designs, read Proof of Stake vs Proof of Work Cryptocurrencies.
Step 5 β Confirmation and Beyond
When a miner includes your transaction in a block, it has one confirmation. Each later block adds another. The Bitcoin developer guide on mining explains that proof-of-work makes transaction history hard to modify, and each new block makes it harder still.
Very rarely, two miners find blocks at nearly the same time and the chain briefly reorganizes. That's why people wait for more confirmations on larger amounts. Exchanges and merchants set their own requirements, so check their policy before a time-sensitive deposit.
You've seen where fees fit into the journey. The next section explains how they are actually calculated, which is where most fee shock comes from.
3. How Bitcoin Transaction Fees Actually Work
Fees Are Based on Size, Not Amount
This is the most important idea in the guide. Bitcoin fees depend on how much block space your transaction uses, not on how much BTC it moves.
Fees work like postage. The stamp price depends on the envelope's size and weight, not on the value inside. A $1 bill and a $1M check cost the same to mail in the same envelope.
This explains the classic complaint: "Why did I pay a big fee to send a small amount?" A small payment built from many small coins can be large in bytes. A huge payment built from one coin can be tiny in bytes.
Hypothetical example: All figures below are illustrative round numbers, not real measurements.
Same size, same fee. Suppose two transactions each use one input and two outputs, and each is 140 vB. Transaction A sends 0.001 BTC. Transaction B sends 10 BTC. Suppose the fee rate is 20 sat/vB.
- Transaction A fee: 140 Γ 20 = 2,800 sats
- Transaction B fee: 140 Γ 20 = 2,800 sats
The amounts differ by a factor of 10,000. The fees are identical.
Same amount, different fee. Now suppose you send 0.05 BTC two ways. Suppose each extra input adds 70 vB.
- With 1 input: 140 vB Γ 20 sat/vB = 2,800 sats
- With 20 small inputs: 140 + (19 Γ 70) = 140 + 1,330 = 1,470 vB. Then 1,470 Γ 20 = 29,400 sats
The 20-input version costs 29,400 Γ· 2,800 = 10.5 times more for the same payment. Paying with one $100 bill is light. Paying with 100 one-dollar coins is bulky and costs more to "ship."
Satoshis per Virtual Byte (sat/vB) Explained
A satoshi (sat) is the smallest unit of bitcoin. The fee rate is the number of satoshis you pay for each virtual byte of your transaction. Miners rank transactions by this number.
A bus with a weight limit is a useful comparison. The driver fills the bus by fare per kilogram, not fare per passenger. A heavy passenger (a transaction with many inputs) must pay more in total to earn the same priority as a light one.
Other blockchains price block space differently. Ethereum, for example, meters computation with "gas," and users choose a tip for the validator. See Ethereum Smart Contracts and Decentralized Applications for that model.
Weight Units, vBytes and the Block Weight Limit
The SegWit upgrade, specified in BIP 141, replaced the old byte-based block size with weight. Weight counts witness data (mostly signatures) at a discount compared with other transaction data. Virtual bytes convert weight back into a byte-like unit, and fee rates are quoted in them.
Each block has a fixed maximum weight. Because signature data is discounted, SegWit and Taproot transactions fit more efficiently and usually cost less.
Explorers show three related numbers. Here is what each means:
- Size: the raw byte count of the transaction.
- Virtual size (vsize): the size used to calculate fees. This is the number that matters to you.
- Weight: the size measured in weight units.
Why Your Address Type Changes Your Fee
Your wallet's address type, also called "script type," changes the size of every input you spend. Sparrow shows it under Settings β Script Type. Electrum shows it under Wallet β Information. Legacy addresses are base58-encoded strings. Newer SegWit and Taproot addresses use a different, lowercase format.
| Address type | Relative input size | Fee impact | Notes |
|---|---|---|---|
| Legacy (P2PKH) | Largest | Highest | Oldest format. No witness discount. |
| Nested SegWit (P2SH-P2WPKH) | Medium | Moderate | A compatibility bridge for older software. |
| Native SegWit (P2WPKH) | Small | Low | Widely supported. A strong default. |
| Taproot (P2TR) | Smallest input | Low | Outputs are slightly larger. Strongest for multi-input and multisig-style spends, with privacy benefits. See BIP 341. |
Exact sizes vary with signature details and with the output types you send to. Use your explorer's vsize field for real numbers.
Inputs, Outputs, and Why Many Small UTXOs Cost More
Each input carries a signature and proof that you can spend the coin. That makes inputs the "heavy" part of a transaction. Outputs are comparatively light.
This has a practical consequence. Frequent small exchange withdrawals and small mining payouts pile up many tiny UTXOs. Every future spend that combines them becomes bulky and expensive. Section 8 explains how to fix this with consolidation.
The Fee Formula, Step by Step
Everything above reduces to one line:
Fee (sats) = virtual size (vB) Γ fee rate (sat/vB)
- Find your transaction's vsize. Most wallets show it on the confirmation screen.
- Choose a fee rate from a live explorer (Section 5 shows how).
- Multiply the two numbers to get the fee in sats.
- To see the fiat cost, switch your wallet's display to BTC or your local currency. Most wallets convert automatically.
Who Sets the Fee?
You do, through your wallet. Miners choose which transactions to accept. The protocol has no fixed price, only a market for block space. The Learn Me a Bitcoin reference site has more detail on transaction structure and weight.
4. Why Fees Rise and Fall: Supply, Demand, and the Block-Space Auction
Fixed Supply: A Steady Pace of Blocks
Bitcoin targets a steady average pace of new blocks, and each block has a fixed maximum weight. The supply of block space barely changes. So almost every fee swing comes from changes in demand.
Ride-share surge pricing works the same way. When a concert lets out, everyone wants a ride at once and prices jump. An hour later, prices fall back.
Demand Spikes: Volatility, Exchanges, Ordinals and Runes
Several kinds of events tend to push fees up:
- Market volatility. During sharp price moves, many users rush to move coins to or from exchanges.
- Exchange activity. Large withdrawal waves and internal wallet consolidations add many transactions at once.
- On-chain data and token protocols. Ordinals inscriptions place data in the witness space of transactions. The later Runes token protocol created its own bursts of demand. Both have at times filled mempools and lifted fee rates sharply.
Weekly and Daily Patterns (A Tendency, Not a Guarantee)
Many users observe that weekends and late-night hours in US and European time zones are often quieter. Quieter periods usually mean lower fee rates.
A fee heatmap by day and hour can show these patterns on historical data. Treat any pattern as a tendency, not a guarantee. A single large event can override it. Always check the live explorer before you send.
Why Fee Estimates Can Be Wrong
- Block times vary. The average pace is steady, but a single gap between blocks can be much longer than usual.
- Surges happen after you broadcast. New higher-paying transactions can push yours further down the queue.
- Wallets estimate differently. They use different algorithms and data sources.
- No estimator can see the future. Every estimate is a forecast, not a promise.
π‘ Takeaway: A fee rate that's fine now can be too low in an hour. That's why RBF exists. Keep it turned on.
Understanding the market is useful. Reading it live is even better, and that's the next skill.
5. How to Read a Mempool Explorer (Hands-On Walkthrough)
Open mempool.space in a new tab now and follow along. Other explorers show similar data with different layouts. The mempool.space FAQ explains every field in more depth.
Projected Blocks and Fee Bands
At the top of the page, you'll see a row of colored blocks. The blocks on the left are projected "mempool blocks." They show the explorer's best guess at the next blocks, based on its own node's mempool. The blocks on the right are blocks that have already been mined.
Each projected block shows a median fee rate and a fee range. The block nearest the divider is the next expected block. If your fee rate sits below the bottom of the last projected block, you have a lot of transactions ahead of you.
Fee Recommendations (No Priority / Low / Medium / High)
The explorer shows four suggested fee rates:
- High Priority: aims for the next block.
- Medium Priority: aims for confirmation within a few blocks.
- Low Priority: expects a longer wait.
- No Priority: may take a long time and can be dropped during congestion.
These are estimates from one node's view of the network. They are a strong starting point, not a guarantee.
Mempool Size and the Purging Threshold
Find the Memory Usage gauge. It shows how much of the node's mempool memory is currently used. When the mempool is full, the minimum fee to get in rises above the normal relay floor.
When this happens, mempool.space shows a "Purging" fee rate. Transactions paying less than that rate are being evicted from the node. Never set a fee below the purging rate if you want your transaction to stay in line.
Looking Up Your Own Transaction (TXID, Fee Rate, Effective Fee Rate, ETA)
- Copy your TXID from your wallet's transaction details screen.
- Paste it into the explorer's search bar and press Enter.
- Read the key fields:
- Status: unconfirmed or confirmed.
- Fee: the total paid, in sats.
- Fee rate: your sat/vB.
- Effective fee rate: the rate including linked parent or child transactions. This matters for CPFP.
- Virtual size: your vsize.
- ETA: the explorer's estimated confirmation time.
- RBF labels: whether the transaction signals replaceability.
If the ETA says hours or days, compare your fee rate with the bottom of the projected blocks. That gap is how far you'd need to bump to move up the queue.
If Your TXID Isn't Found
The explorer's node may have dropped your transaction, or it may never have received it. Search the TXID on a second explorer before you worry. If neither explorer has it, your wallet may need to rebroadcast it.
Interactive Exercise: Find Today's Next-Block Fee Rate and Estimate Your Cost
π§ͺ Try it now (about 10 minutes)
- Write down the current High Priority rate: ______ sat/vB
- Open your wallet's send screen and note the vsize of a typical send from your wallet: ______ vB
- Multiply: ______ vB Γ ______ sat/vB = ______ sats
- Switch your wallet's display to your local currency to see the fiat cost: ______
- Repeat with the Low Priority rate: ______ vB Γ ______ sat/vB = ______ sats
- Subtract the two results to see what patience saves you today: ______ sats
6. Choosing the Right Fee: A Decision Framework
You can now read the market. The next step is turning that reading into a fee decision.
Interactive: How Urgent Is Your Transaction?
Pick your path:
Urgent: Paying for the Next Block
Use this path for time-sensitive exchange deposits, payment deadlines, or closing a trade.
- Open the explorer and read the High Priority rate.
- If the memory gauge is climbing quickly, add a small buffer above that rate.
- In your wallet, choose a custom sat/vB instead of the "fast" preset.
- Make sure RBF is on, so you can bump again if needed.
- Read the total fee in sats and fiat before you sign.
Standard: Within a Few Hours
This path fits most everyday payments.
- Use the Medium or Low Priority rate.
- Keep RBF on.
- Check the explorer after an hour or two.
- Bump only if your fee rate has fallen well below the projected blocks.
Patient: Low-Fee Strategies and Timing
This path suits moving coins between your own wallets or consolidating UTXOs.
- Pick a rate near the bottom of the projected blocks, safely above any current purging rate.
- Send during quieter periods when possible.
- Keep RBF on as insurance.
- Expect that your wallet may need to rebroadcast if mempools drop the transaction.
Wallet Fee Settings Compared (Presets vs. Custom sat/vB vs. Coin Control)
| Setting | Pros | Cons | Commonly found in |
|---|---|---|---|
| Presets (slow / medium / fast) | Easy, one tap | Opaque. Can overshoot or lag during spikes. | Most mobile wallets, including BlueWallet |
| Custom sat/vB | Precise. You match the live market. | Needs a quick explorer check | Sparrow, Electrum, BlueWallet, Bitcoin Core |
| Coin control (choose which UTXOs to spend) | Smallest size and fee, plus privacy control | More advanced | Sparrow, Electrum, Bitcoin Core |
π Rule of thumb: Check the explorer β pick your urgency β set a custom sat/vB β keep RBF on.
7. How to Fix a Stuck Bitcoin Transaction
Interactive: Are You the Sender or the Receiver?
Start here:
- π€ I'm the sender, and my wallet offers "Bump fee" or "Increase fee" β Method 1: RBF
- π₯ I'm the receiver, or a sender with a change output β Method 2: CPFP
- π€· Neither option works for me β Method 3: Wait or rebroadcast, or Method 4: A reputable accelerator
First, Don't Panic: What "Unconfirmed" Really Means
"Unconfirmed" means no miner has put the transaction in a block yet. The coins can only end up with your intended recipient or stay under your control. Run three quick checks first:
- Look up the TXID on two different explorers.
- Compare your fee rate with the current projected blocks.
- Check whether your wallet shows a "Bump fee" or "Increase fee" option on the transaction.
Method 1 β Replace-By-Fee (RBF), Step-by-Step
RBF is like re-bidding your standby ticket. You swap your ticket for a pricier one on the same seat, and the old ticket becomes invalid. Technically, you broadcast a new version of the transaction that spends the same inputs at a higher fee.
- Open the unconfirmed transaction in your wallet.
- Choose the fee-bump option. Labels vary by version:
- Sparrow: Transactions tab β right-click the transaction β Increase Fee (RBF)
- Electrum: History tab β right-click β Increase fee (some versions say "Bump fee")
- BlueWallet: tap the transaction β Bump Fee
- Bitcoin Core GUI: Transactions tab β right-click β Increase transaction fee
- Check the explorer and set a new sat/vB that reaches the projected block you want.
- Review the total fee, then sign and broadcast.
- Search the new TXID on an explorer. The old TXID should disappear or show as replaced.
Under BIP 125, a replacement must pay a higher total fee and a higher fee rate than the original. It must also pay enough extra to cover its own relay. Your wallet handles these rules automatically. The Bitcoin Optech RBF topic page covers the details.
Opt-In RBF vs. Full-RBF
Originally, RBF was opt-in. A transaction had to signal that it was replaceable, as defined in BIP 125. Without that signal, most nodes refused to relay replacements.
Newer Bitcoin Core releases have moved toward full-RBF, where nodes relay valid replacements even without the opt-in signal. Check the Bitcoin Core release notes for your node's version. In practice, replacing your own unconfirmed transaction is now easier. Your wallet still has to support building the replacement.
Cancelling a Transaction with RBF
A "cancel" is really a replacement. The wallet builds a new transaction that sends the coins back to your own address at a higher fee. Sparrow offers Cancel Transaction, and BlueWallet offers a cancel option on eligible transactions. This only works before confirmation. Once a transaction confirms, it cannot be reversed.
Method 2 β Child-Pays-For-Parent (CPFP), Step-by-Step
CPFP is a child paying the family's fare. You spend an unconfirmed output in a new "child" transaction with a high fee. A miner can only collect the child's fee by also including the parent, so the whole package boards together.
The receiver can use CPFP on the incoming output. A sender can use it on their own change output.
- Find the unconfirmed incoming output (or your change output) in your wallet.
- Choose the CPFP option. In Electrum: right-click β Child pays for parent. In Sparrow: right-click β Increase Effective Fee (CPFP).
- Set the fee so the combined package reaches your target rate. Most wallets calculate this for you.
- Sign and broadcast the child.
- On the explorer, check the parent's effective fee rate. It should now reflect the package.
Hypothetical example: All figures are illustrative.
Suppose the stuck parent is 140 vB and paid 2 sat/vB. Its fee is 140 Γ 2 = 280 sats. Suppose your child transaction is 110 vB, and you want the package to reach 30 sat/vB.
- Package size: 140 + 110 = 250 vB
- Package fee needed: 250 Γ 30 = 7,500 sats
- Child fee: 7,500 β 280 = 7,220 sats
- Child's own rate: 7,220 Γ· 110 β 65.6 sat/vB
Lesson: CPFP works, but it usually costs more than RBF because you pay for two transactions' worth of space.
The Bitcoin Optech CPFP topic page explains the mechanics further.
Method 3 β Waiting It Out or Dropping From Mempools
If your fee rate is close to the projected blocks, waiting is often the best choice. It will likely confirm when demand eases.
If your rate is below the purging threshold, nodes may evict it. Bitcoin Core also expires old transactions after its default mempoolexpiry period. After a transaction drops, the coins show as spendable again. Some wallets need a rescan, a resync, or a "remove transaction" action first.
One warning: your wallet or another node may rebroadcast the dropped transaction. If you want certainty, replace it with RBF rather than assuming it is gone.
Method 4 β Transaction Accelerators (Pros, Cons, Trust Caveats)
Accelerators are services that pay or ask mining pools to prioritize your transaction. For example, mempool.space offers an acceleration service, and some mining pools run their own.
- Pros: works even when you can't use RBF or CPFP.
- Cons: costs can be high, only participating pools help, you rely on a third party, and many fake accelerator sites exist.
π« Hard rule: A legitimate accelerator needs only your TXID and a payment. It never needs your seed phrase or private keys.
Comparison Table: RBF vs. CPFP vs. Accelerator vs. Waiting
| RBF | CPFP | Accelerator | Waiting | |
|---|---|---|---|---|
| Who can use it | Sender | Receiver, or sender with change | Anyone | Anyone |
| Cost | Lowest bump | Higher (pays for two) | Variable, often highest | Free |
| Speed | Fast once rebroadcast | Fast once the package relays | Depends on participating pools | Unpredictable |
| Requirements | Wallet support for replacement | A spendable unconfirmed output | TXID and payment | Patience |
8. Advanced Fee-Saving Strategies
Fixing a stuck transaction solves today's problem. The strategies below help you avoid tomorrow's.
Use Native SegWit or Taproot Addresses
Native SegWit and Taproot inputs are much smaller than Legacy inputs, so typical sends cost noticeably less. Moving coins off a Legacy wallet costs one transaction fee, but every later spend is cheaper. Do the move during a low-fee period. A dedicated SegWit vs. Taproot guide is coming soon.
Consolidate UTXOs When Fees Are Low
Consolidation means sending many small coins to yourself in one transaction, so they become one larger coin. Do it when the explorer shows a near-empty mempool and low fee rates.
Hypothetical example: All figures are illustrative.
Suppose spending your 20 small coins creates a 1,470 vB transaction, matching the earlier example in Section 3.
- Consolidate now at 2 sat/vB: 1,470 Γ 2 = 2,940 sats
- Later payment with one coin at 20 sat/vB: 140 Γ 20 = 2,800 sats
- Total with consolidation: 2,940 + 2,800 = 5,740 sats
- Without consolidation, paying later at 20 sat/vB: 1,470 Γ 20 = 29,400 sats
- Savings: 29,400 β 5,740 = 23,660 sats
Consolidation has a privacy cost, because it publicly links the merged coins. See Section 9 before you consolidate.
Batch Multiple Payments
Batching sends several payments in one transaction with many outputs. The inputs and fixed overhead are shared, and each extra output adds only a small amount of size. This matters most for businesses, payroll, and exchanges. It's also a good reason to prefer exchanges that batch withdrawals.
Move Small Payments to Lightning
The Lightning Network is a payment layer built on Bitcoin. Payments inside channels happen off-chain, so they don't wait in the mempool. Opening and closing channels are on-chain transactions, so those steps are still affected by fees. The Lightning Network documentation covers the protocol. A dedicated Lightning guide is coming soon.
| On-chain | Lightning | |
|---|---|---|
| Settlement speed | Depends on fee rate and block timing | Typically near-instant |
| Fee behavior | Set by the block-space market | Usually small routing fees |
| Mempool sensitivity | High | Only for channel opens and closes |
| Best for | Large amounts, long-term storage moves | Small, frequent payments |
| Setup | Any Bitcoin wallet | Channels and liquidity, or a custodial or non-custodial Lightning wallet |
Exchange Withdrawal Fees vs. Network Fees
Exchanges often charge their own withdrawal fee. It may be higher or lower than the actual network fee, and the exchange may batch your withdrawal with others. A high exchange fee is the exchange's pricing, not the mempool's fault. To save money, compare exchanges, withdraw less often in larger amounts, and use Lightning withdrawals where offered.
9. Security Best Practices
Panic about a stuck transaction makes people easy targets. These habits keep you safe.
Stuck-Transaction Scams and Fake Accelerators
Fake "support agents" on X, Telegram, Discord, and Reddit target users who post about stuck transactions. Fake accelerator sites do the same. Watch for these red flags:
- Unsolicited direct messages offering help
- Any request for your seed phrase or private keys
- "Wallet sync" or "wallet validation" websites
- Requests to send more BTC to "unlock" your funds
π Hard rule: Never share your seed phrase or private keys to unstick a transaction. No legitimate fix needs them. RBF and CPFP happen inside your own wallet.
Merchants and Zero-Confirmation Payments
With full-RBF relay now widespread, an unconfirmed payment can be replaced more easily, for example to send the coins back to the payer. Wait for at least one confirmation before releasing anything valuable. For instant point-of-sale payments, use Lightning instead.
Verify TXIDs on Several Explorers
Each explorer reflects its own node's mempool. Cross-check important transactions on at least two. Running your own node gives you the most accurate and private view.
Privacy When Consolidating and Looking Up Transactions
Consolidating links coins publicly as likely belonging to the same owner. Avoid merging coins from identity-verified (KYC) sources with coins from other sources. Consider consolidating by source.
Looking up your TXID or address on a public explorer also tells that service you're interested in it. Your own node avoids this leak.
10. The Mempool and Bitcoin's Future
Fees as Miner Security Budget After Halvings
Miners earn two things: the block subsidy (newly issued bitcoin) and transaction fees. Bitcoin's maximum supply is capped at 21,000,000 BTC, and the subsidy shrinks on a fixed halving schedule. CoinGecko lists 20,113,243 BTC in circulation at the time of writing.
The Bitcoin whitepaper anticipates that the incentive can shift over time toward transaction fees. As issuance declines, fees are expected to make up a larger share of what pays miners to secure the network. For background, see Exploring Bitcoin's Foundations. A dedicated halving guide is coming soon.
Ongoing Improvements: Package Relay, TRUC/v3 Transactions, Cluster Mempool
- Package relay: lets nodes evaluate a parent and child together. A low-fee parent is then less likely to be rejected before its high-fee child can rescue it, which makes CPFP more reliable. See Bitcoin Optech on package relay.
- TRUC transactions (Topologically Restricted Until Confirmation, also called "v3"): an opt-in format with limits that make fee bumping more predictable. It is especially useful for Lightning and other layer-2 protocols. See Bitcoin Optech on v3 relay.
- Cluster mempool: a redesign of how Bitcoin Core groups and orders related transactions. It aims to make eviction, block building, and fee-bumping rules more consistent. It has been in development and rolling out across versions. See Bitcoin Optech on cluster mempool.
What this means for you: you don't need to do anything. Over time, these upgrades make fee bumping more reliable and Lightning more robust.
β οΈ Common Mistakes to Avoid
- Fee below the minimum relay or purging rate. Why it hurts: the transaction may never spread, or it may be evicted quickly. Do this instead: check the explorer's minimum and purging rate before you send.
- Disabling RBF, then getting stuck. Why it hurts: your wallet may refuse to build a replacement. Do this instead: keep RBF on. Full-RBF relay helps, but your wallet must still support replacement.
- Collecting dust-sized UTXOs. Why it hurts: tiny outputs can cost more to spend than they're worth. Do this instead: avoid tiny withdrawals and payouts. Use coin control to freeze dust, which also defends against privacy-targeting "dust attacks."
- Trusting the "fast" preset during a spike. Why it hurts: presets can overshoot or lag the market. Do this instead: set a custom sat/vB from the live explorer.
- Panic-resending from a different wallet. Why it hurts: importing your seed elsewhere and re-sending can create conflicting double-spends and confusing balances. Do this instead: use RBF from the original wallet.
- Confusing the exchange's fee with the network fee. Why it hurts: you blame the mempool for the exchange's pricing. Do this instead: compare exchange withdrawal fees separately (see Section 8).
- Fee-rate typos. Why it hurts: typing two extra zeros multiplies your fee by 100, and a confirmed fee can't be undone. Do this instead: always read the total fee in sats and fiat before signing.
Frequently Asked Questions
What is the bitcoin mempool in simple terms?
The bitcoin mempool is a waiting room for transactions that are valid but not yet in a block. Each node keeps its own copy. Miners generally pick the highest fee-rate transactions first, so lower-paying ones wait longer. See Section 3 for how fee rates work.
How long can a bitcoin transaction stay in the mempool?
It depends on each node's settings. Bitcoin Core has a default memory cap and a default expiry period, and operators can change both. Low-fee transactions can be evicted early when mempools fill up. Wallets and nodes may also rebroadcast transactions, so one can reappear after expiring.
Why is my bitcoin transaction unconfirmed?
Usually, your fee rate is below what miners are currently choosing. Other transactions paying more per vbyte are ahead of yours. Compare your sat/vB with the explorer's projected blocks. Then bump with RBF or CPFP, or wait for demand to ease.
What is a good sat/vB fee right now?
No fixed number is correct, because the market changes constantly. Open a live explorer and read the High, Medium, and Low Priority rates. Choose based on urgency, and stay above any purging rate. Section 6 walks through each choice.
Can a bitcoin transaction be cancelled once it's in the mempool?
Only before it confirms. A "cancel" is an RBF replacement that sends the coins back to your own address at a higher fee. Once the transaction is in a block, it cannot be reversed.
Why did I pay a high fee to send a small amount of bitcoin?
Fees depend on transaction size in vbytes, not on the amount sent. If your wallet combined many small UTXOs, the transaction was large. Legacy addresses also make inputs bigger. Consolidating and using Native SegWit or Taproot reduces future fees.
Does the bitcoin mempool ever get empty?
Yes, at times. During quiet periods, even very low fee rates can clear quickly. These periods are ideal for consolidating UTXOs or making non-urgent transfers.
What happens to my bitcoin if a transaction is dropped from the mempool?
The coins stay at the original address, because the transaction never confirmed. Your wallet may need a rescan or a "remove transaction" action before it shows them as spendable. Watch for rebroadcasts, and use RBF if you want certainty.
Are Lightning Network fees affected by the mempool?
Payments within Lightning channels mostly aren't, because they happen off-chain. Opening and closing channels are on-chain transactions, so they are affected. Forced channel closes are affected too.
Who sets bitcoin transaction fees?
The sender chooses the fee through their wallet. Miners decide which transactions to include. The market for block space sets the going rate. No central authority sets fees.
What's Next?
Key takeaways:
- Unconfirmed bitcoin is waiting, not lost.
- Fees equal vsize Γ sat/vB. They are not a percentage of the amount.
- Check a live explorer before every send.
- Keep RBF turned on.
- Consolidate during quiet periods, and use SegWit or Taproot to save long-term.
Action checklist: (1) bookmark mempool.space; (2) check your wallet's script type; (3) turn on RBF; (4) review your UTXOs; (5) try a small Lightning payment.
Now that you've completed this guide, you might want to:
- Deepen your foundation with Bitcoin: The First Cryptocurrency Deep Dive
- Understand the mining side of fees in Proof of Stake vs Proof of Work Cryptocurrencies
- Review how proof-of-work secures the ledger in Unpacking Bitcoin: Origins, Technology, and Impact Explained
- Revisit the basics in Bitcoin Origins and Mechanics Explained
- Coming soon: How to Use Sparrow Wallet, Lightning Network Guide, Understanding UTXOs and Coin Control, Bitcoin Halving Explained, Run Your Own Bitcoin Node, and SegWit vs. Taproot
Further reading: Bitcoin developer documentation, Bitcoin Core release notes, BIP 125, BIP 141, BIP 341, mempool.space FAQ, Bitcoin Optech topics, Learn Me a Bitcoin, and the Bitcoin whitepaper.
The bitcoin mempool no longer has to be a mystery. Next time your wallet shows a fee, you'll know exactly where that number came from and whether to accept it.
Sources
- Bitcoin Developer Guide, Transaction Broadcasting
- Ethereum β primary documentation
- Decentralized Exchange β primary documentation
- Ethereum β official documentation site
- xrpl.org
- Tron β primary documentation
- Bitcoin β primary documentation
- Cardano β primary documentation
- Cardano β official documentation site
- Tron β official documentation site
- Bitcoin β primary documentation
- Ethereum β primary documentation
- BNB Chain β primary documentation
- Ethereum β primary documentation
- Avalanche β primary documentation
- Polkadot β primary documentation
- XRPL History
- Polkadot β primary documentation
- XRP Ledger β primary documentation
- BNB Chain β primary documentation