What Is a Mempool? Why Your Transaction Gets Stuck

The mempool is where every unconfirmed cryptocurrency transaction goes to wait its turn for inclusion in the next block. Think of it as a crowded waiting room at a concert venue — everyone has a ticket (a valid transaction), but only so many people get through the door at once. If you showed up with a cheap ticket during peak hours, you might be standing in that lobby for a very long time. This article covers how the waiting room works, why some transactions get prioritized over others, and what you can do when your money is stuck in digital limbo.

The Mempool Is Not a Queue — It’s a Competitive Marketplace

Here’s the first misconception to discard: the mempool is not a first-come, first-served system. Many newcomers assume that whichever transaction broadcasts first gets confirmed first. This is wrong, and understanding why will save you some frustration.

When you send a Bitcoin or Ethereum transaction, it propagates to nodes across the network. Each node maintains its own version of the mempool, and these mempools aren’t identical. A node in Singapore might have a different set of pending transactions than one in Germany, simply due to network latency and which transactions reached them first.

What actually determines confirmation order is the fee rate — the amount you’re paying per unit of block space. This is expressed in satoshis per virtual byte (sat/vB) for Bitcoin or gwei for Ethereum. Miners and validators are economically motivated to fill blocks with the highest-fee transactions first. They’re running businesses, not public services.

This is why during network congestion, a transaction with a $2 fee might confirm in minutes while one with a $0.50 fee sits for days. The math is brutal and impersonal. There is no customer service line.

How Transactions Actually Get Confirmed

When you hit send, your wallet broadcasts the transaction to the nearest node. That node validates the transaction — checking that you actually have the funds, that the signature is valid, and that nothing about the transaction breaks the protocol rules.

If validation passes, the transaction enters that node’s mempool. That node then propagates the transaction to its peers, who do the same thing. Within seconds, most connected nodes have your transaction in their mempool. This is why you often see a transaction as “pending” almost immediately — it’s in the mempool, but that doesn’t mean it’s close to confirmation.

From there, your transaction waits. Every few seconds, a miner or validator (depending on the blockchain) selects transactions from the mempool to fill the next block. They sort by fee rate, highest first. If your transaction’s fee rate places you below the cutoff — the “fee floor” — you don’t make the block. You wait for the next one.

On Bitcoin, blocks are limited to roughly 4 million weight units (approximately 2-4 MB of data depending on transaction types). On Ethereum, block space varies but averages around 15-30 transactions per block in normal conditions. When demand exceeds supply, fees spike, and the waiting begins.

Why Network Congestion Happens and Who Causes It

Network congestion isn’t random. It follows predictable patterns, and understanding these patterns helps you avoid stuck transactions or time your sends strategically.

Bitcoin congestion typically spikes during U.S. market hours (9:30 AM to 4 PM EST) and Asian market hours (especially Tokyo and Hong Kong sessions). Data from mempool.space shows that median fee rates often double during these windows. More people are transacting during these periods, competing for the same limited block space.

But there’s a subtler factor at play. When Bitcoin’s price moves significantly, transaction volume surges. During the April 2024 price rally above $67,000, Bitcoin’s mempool swelled to over 400,000 unconfirmed transactions. Average fee rates jumped from 15 sat/vB to over 150 sat/vB within 24 hours. Anyone who set their fee based on the previous week’s rates was in for a nasty surprise.

Ethereum congestion follows different rhythms. Smart contract interactions — especially token launches, NFT mints, and DeFi protocol activities — can fill blocks to capacity. The 2024 Bitcoin ETF approval week saw Ethereum gas fees briefly spike above 200 gwei for standard transfers, roughly 10x the normal rate.

The people causing the congestion aren’t always who you’d think. Yes, some are regular users moving funds. But a significant portion of mempool pressure comes from automated trading bots, arbitrageurs, and protocol interactions. These actors pay high fees consistently, effectively raising the floor for everyone.

Fee Dynamics: The Actual Math Behind Your Transaction Cost

Wallet fee estimates are notoriously unreliable. Understanding why helps you set better fees.

Most wallets use one of three methods to estimate fees: historical averages, current network data, or a combination of both. Historical averages are useless during sudden congestion events — they’re based on last week’s conditions, not today’s reality. Current network data is better, but by the time your wallet queries the network, the situation may have already shifted.

Fee estimation is genuinely hard. The mempool is constantly in flux. A block just confirmed that included 3,000 transactions, clearing out the high-fee backlog. Now the fee floor has dropped. Your wallet sees the current low fees and suggests a conservative amount. But within the next hour, a large exchange might process its daily batch of withdrawals, pushing fees back up.

For Bitcoin specifically, the fee rate you pay depends on three variables: the transaction’s data size (in weight units), the current fee market, and your urgency. A simple one-input, one-output transaction might be around 250 bytes. A complex transaction with multiple inputs — say, consolidating many small UTXOs — could be 1,000 bytes or more. The fee in satoshis is the rate multiplied by the size.

Here’s a concrete example: a 250-byte transaction at 50 sat/vB costs 12,500 satoshis, or about $4.50 at current Bitcoin prices. The same transaction at 200 sat/vB costs $18. During the November 2022 FTX collapse, median fees peaked at over 300 sat/vB, making that simple transfer cost nearly $30.

Ethereum fees work differently. You pay for gas, which is computed as gas limit multiplied by gas price. The gas price (in gwei) fluctuates based on demand. A simple ETH transfer has a gas limit of 21,000. At 50 gwei, that’s roughly $3. At 500 gwei (during congestion), it’s $30. Smart contract interactions can use 100,000 to 500,000 gas or more, multiplying those costs significantly.

Why Low-Fee Transactions Get Stuck Indefinitely

A transaction doesn’t just get politely forgotten if it sits in the mempool too long. It gets evicted — eventually.

Each node sets its own mempool size limits and eviction policies. Most Bitcoin nodes use a policy called Memory Pool Limit (maxmempool), which defaults to 300 MB. When the mempool fills up, nodes start evicting the lowest-fee transactions. This is called trimming, and it’s brutal: if you’re at the bottom of the fee list, you’re first out.

Once your transaction is evicted from a node’s mempool, it effectively disappears from the network. Your wallet might still show it as “pending,” but nodes are no longer rebroadcasting it. The transaction hasn’t failed — it simply no longer exists in the collective memory of the network.

For Ethereum, the dynamics are similar but with a twist. Ethereum’s execution layer clients (like Geth) have configurable mempool limits. During the 2021 NFT boom, some users reported transactions that simply never confirmed, even after days of waiting. The transactions were valid, but they kept getting priced out of every block.

Stuck transactions can prevent you from sending subsequent transactions. This happens because most wallets use a nonce-based system — your transaction has a sequence number, and you can’t send a new transaction with the same sender and a higher nonce until the previous one confirms or gets replaced. If your stuck transaction is nonce #5, and you try to send nonce #6, most wallets will either refuse to broadcast it or will broadcast it with the same low fee, ensuring it also gets stuck.

Replace-by-Fee: The Official Escape Hatch

Replace-by-fee (RBF) is a protocol feature that lets you resend the same transaction with a higher fee. It’s the most reliable way to unstick a transaction, but it requires setup before you need it.

When you create a transaction in a wallet that supports RBF, you can enable it in the settings. This adds a flag to the transaction telling nodes “this can be replaced if a higher-fee version shows up.” When you later want to speed up the transaction, you create a new transaction that spends the same inputs (same coins going to the same recipient, or to yourself) but pays a higher fee.

RBF is opt-in. Many wallets have it disabled by default because it confuses users. If your transaction was sent without the RBF flag, you can’t replace it. Check your wallet’s RBF settings before sending.

Bitcoin wallets like Electrum, Sparrow, and BlueWallet support RBF. You can typically bump the fee by right-clicking the transaction and selecting “increase fee” or “bump fee.” The wallet constructs a new transaction that pays more but spends the same inputs. Once the new transaction confirms, the old one becomes invalid — double-spend prevention ensures only one can go through.

Ethereum doesn’t have a direct RBF equivalent, but it has something better: nonce management. If you have a stuck transaction, you can send a new transaction with the same nonce but a higher gas price. This replaces the stuck transaction. Most Ethereum wallets (including MetaMask) handle this automatically if you try to send while a transaction is pending — they’ll usually offer to “speed up” the transaction, which does exactly this.

Child Pays for Parent: An Alternative Speed-Up Method

Child Pays for Parent (CPFP) is a technique that works even if RBF isn’t enabled. The idea is simple: you create a new transaction that spends the unconfirmed transaction’s output, and you pay a high enough fee on the new transaction to cover both.

Think of it as bribing the miner with a tip that applies to both transactions. The parent transaction (the stuck one) pays a low fee, but the child transaction pays a high fee. Miners want the high-fee child, so they’ll include both to get it.

This works because miners earn the total fees from all transactions in a block. If the combined fees are attractive enough, they’ll pull in both transactions. The math needs to work out: the child’s fee must compensate for the parent’s low fee while also covering its own block space.

CPFP is more complex to execute manually, but some wallets automate it. Ledger Live, for instance, has a “Child Pays for Parent” option for Bitcoin transactions. For Ethereum, you accomplish the same thing by sending a new transaction with a higher gas price that spends from the same address.

One limitation: this only works if the stuck transaction’s output is spendable. If you sent funds to an external address you don’t control, CPFP won’t help. And if the transaction was already evicted from most nodes’ mempool, CPFP won’t work either because the parent is effectively gone.

The Waiting Game: How Long Is Too Long

If you decide to wait out a stuck transaction, you might be wondering how long it could take. The answer depends, and the worst-case scenarios are ugly.

Bitcoin transactions don’t technically expire. A transaction is valid as long as the inputs are unspent, which could theoretically be years. However, nodes evict low-fee transactions after a period of inactivity, typically 72 hours to two weeks, depending on the node’s configuration and current mempool pressure.

During extreme congestion events, eviction happens much faster. In January 2024, when Bitcoin ordinal inscriptions were at peak popularity, some low-fee transactions were evicted within hours. People who paid 1 sat/vB saw their transactions disappear from their wallets within a day.

For Ethereum, there’s no hard expiration either, but most nodes drop transactions that haven’t been confirmed within roughly 3 to 6 hours of being in the mempool. During the 2023 Jupiter aggregator launch, transactions with fees below 100 gwei were being dropped within minutes of submission.

If a transaction sits for more than 24 hours without confirmation, your best move is to assume it won’t confirm and take action. Either RBF, CPFP, or wait for the network to eventually evict it (which frees up your coins to send again).

Common Mistakes That Cause Stuck Transactions

Most stuck transactions result from a handful of predictable errors. Avoid these, and you’ll almost never have a problem.

The most common mistake is setting fees too low based on historical data. Using a fee estimate from the previous day during a congestion event is a guaranteed way to get stuck. Always check current mempool conditions before sending.

The second mistake is not enabling RBF. Many wallets have it hidden in advanced settings, and users don’t realize they need it until it’s too late. Go into your wallet settings right now and make sure RBF is enabled for future transactions.

Third, some users try to save money by setting a custom fee manually without understanding the current market. They see a suggestion of 10 sat/vB and think “that seems high, I’ll set it to 2.” Sometimes that works. Most of the time, it doesn’t.

Fourth, double-spending yourself by accidentally sending two transactions with overlapping inputs can cause both to get stuck. This happens when users hit send twice or when a wallet has a bug. Only one will confirm (whichever has the higher fee), but both will compete for block space and clog the mempool.

Finally, using exchanges with inadequate fee policies can trap you. Some exchanges batch withdrawals and pay low fees on behalf of users. If you’re withdrawing from an exchange and your transaction gets stuck, you’re at the mercy of the exchange’s policy. You usually can’t RBF a transaction you didn’t create yourself.

What Actually Happens to Stuck Transactions Over Time

Stuck transactions don’t always resolve neatly. Sometimes they confirm hours later after network conditions change. Sometimes they’re evicted and your coins reappear in your wallet. Sometimes they’re in a weird middle state where your wallet shows them as pending but the broader network has forgotten them.

If your transaction has been stuck for more than 48 hours, the safest approach is to assume it won’t confirm. Check your wallet’s transaction details — if it shows as “unconfirmed” but you can find no evidence of it on a block explorer, it’s likely been evicted. In this case, your wallet should eventually “forget” about it and let you spend those coins again.

However, if you manually created a transaction with a specific nonce and it got stuck, your wallet might refuse to let you send anything else from that address. The fix is to either use RBF/CPFP to push it through or to reset the wallet’s transaction cache (which varies by wallet).

Block explorers like mempool.space for Bitcoin and Etherscan for Ethereum are invaluable here. They show you exactly what’s in the mempool, what the current fee rates are, and whether your transaction is still floating around. If a block explorer can’t find your transaction, it’s effectively gone.

Looking Forward: What Changes Are Coming

The mempool experience is slowly improving, but it’s not solved yet.

Bitcoin’s upcoming innovations include package relay, which would let users submit parent and child transactions together, solving some of the CPFP limitations. There are also ongoing discussions about anchor outputs (already partially implemented in Taproot) that make CPFP easier by ensuring child transactions always have a spendable output.

Ethereum’s transition to blob transactions (EIP-4844, deployed in March 2024) has already significantly reduced costs for rollup transactions. While this doesn’t directly change the mempool for L1 transactions, it shifts a lot of activity off the main chain, reducing congestion overall.

For users, the best strategy tends to be the same: always enable RBF, check current fee conditions before sending, and don’t skimp on fees during volatile periods. The mempool isn’t going away, and understanding how it works is part of being a competent crypto user.

The stuck transaction problem is fundamentally an economic one — limited supply, competing demand, and rational actors prioritizing profit. There’s no magic solution coming that will make fees disappear. What there is, is better tooling, better understanding, and better user habits. You’re already ahead by reading this far.