Glossary

    Glossary

    Mempool

    The mempool is the waiting room where broadcast transactions sit until a miner or validator includes them in a block. It is why a transfer says pending - and why the fee you attach decides how long the wait lasts.

    FoundationsLast reviewed 2026-10-01

    What it is

    The mempool - short for memory pool - is the queue of transactions that have been broadcast to the network but not yet included in a block. Every node keeps its own copy: when your wallet sends a transaction, it lands in the mempool of every node that receives it, and it waits there until a miner or validator picks it up. Picking is not first-come-first-served. Miners select transactions by fee rate, which makes the fee you attach your position in the queue.

    The queue has no single shared view, which is why two block explorers can disagree about a transaction's status. A transaction can also sit indefinitely: most nodes eventually drop transactions that linger too long, and on Bitcoin a stuck transfer can usually be replaced with a higher-fee duplicate through replace-by-fee. Ethereum's version prices block space with an algorithmic base fee, and transactions bidding below it simply wait until the price falls. Pending does not mean failed - it means waiting.

    Key takeaways

    • The mempool is the queue of broadcast transactions not yet included in a block.
    • Miners and validators pick transactions by fee rate, so the fee is your queue position.
    • There is no single shared queue - every node keeps its own view.
    • A stuck Bitcoin transfer can usually be replaced with a higher-fee duplicate through replace-by-fee.
    • Pending means waiting, not failing - the transaction sits in the queue until included or dropped.

    How it works

    Walk one full trip on Bitcoin. Your wallet signs a transfer and broadcasts it; every node that receives it checks the signature and adds it to its own mempool. Miners assembling the next block sort the queue by fee rate - satoshis per unit of transaction size - and fill the block with the highest bidders. A transfer attached at 1 satoshi per vbyte during quiet hours confirms in the next block; the same rate during congestion sits for hours while higher bidders jump the queue. If it sits too long, most nodes eventually forget it and the transfer drops back to your wallet as unsent.

    The fix for a stuck transfer is replace-by-fee: broadcast a duplicate of the same transaction with a higher fee, and nodes replace the old version in their mempools. Ethereum runs a different auction - EIP-1559 sets an algorithmic base fee for block space that rises with congestion and falls with quiet, and transactions bidding below the current base fee wait until it drops. The block entry covers what happens the moment a transaction is picked.

    For Australian readers, the mempool is the honest answer to every pending deposit: the exchange is not slow, the fee was low, and the queue is visible on any explorer. The transaction-id entry covers how to find your transfer and read its status.

    Why it matters

    The mempool matters at the exact moment a transfer says pending, which for Australian buyers is usually a deposit to an exchange - often placed during Australian evening hours, which overlap with peak congestion in other time zones. A colleague named Brent (yes, that Brent) watched a deposit sit pending for 40 minutes, assumed the worst, and sent it again; the duplicate was a second real deposit and a week of support emails. The mempool was the delay both times, and nobody had told him pending means waiting.

    The highest-leverage habits are a realistic fee, an explorer check before reacting, and replace-by-fee instead of a duplicate. Attaching a near-zero fee during congestion costs hours; re-sending the same transaction at the same fee costs the same hours twice. The block-confirmation entry covers what the confirmation count means once the transaction is picked, and the difference between waiting and failing. One block cycle is the wait; two is the exception.

    Real-world examples

    A stuck Bitcoin transfer, diagnosed and fixed

    A transfer attached at 1 satoshi per vbyte during a congestion spike sat unconfirmed for three hours. The explorer showed it sitting in the mempool with a lower fee rate than the going price for block space. A replace-by-fee duplicate at 12 satoshis per vbyte replaced it within minutes, and it confirmed in the next block. Total cost of the fix: the fee difference, a few dollars - against a week of support emails avoided.

    An Ethereum swap during a memecoin frenzy

    A swap quoted at 15 gwei was broadcast during a token launch, and the base fee spiked past 60 gwei within minutes. The transaction sat in the mempool bidding below the going rate while the quote expired. Rather than replacing it, the sender waited for the frenzy to pass and the base fee to fall, and the swap confirmed four hours later at the original fee. Patience is a fee strategy; replace-by-fee is the other one.

    The deposit that was never actually slow

    An exchange deposit showed pending for 40 minutes and the sender assumed the platform was broken. The transaction ID on a block explorer showed zero confirmations and a fee rate near the bottom of the queue - the wallet-address entry covers finding the right address to check. The deposit confirmed on its own once a miner picked it, and no support ticket was needed. Pending was the mempool doing its job.

    Common mistakes

    Mistake: Sending a duplicate transfer because the first shows pending.

    Why it bites you: Pending means the transaction is in the queue, not lost. Brent's duplicate was a second real deposit and a week of unwinding it with support.

    Mistake: Attaching a near-zero fee during congestion.

    Why it bites you: The fee rate is the queue position. A near-zero bid during a spike means hours in the mempool while higher bidders confirm first.

    Mistake: Trusting one explorer's mempool view as the whole queue.

    Why it bites you: Every node keeps its own view and explorers approximate it. Two explorers can disagree about a transaction that is in one mempool and not another.

    Mistake: Assuming a stuck transaction will cancel itself.

    Why it bites you: Most nodes eventually drop stale transactions, but the timing is nobody's promise. Replace-by-fee is the actual fix; waiting is the fallback, not the plan.

    Ivy's take

    I watched a mempool for a week so you don't have to, and the market underneath it is a blind auction nobody advertised: every block is a fixed amount of space, and the fee rate is the bid. The pattern that surprised me is how predictable the congestion is - it clusters around the same hours, and the fee market reprices within minutes.

    The recurring Brent conversation is the duplicate transfer, which is the one mistake in this entire glossary that costs real money out of pure impatience. My position: set a realistic fee, check an explorer, and drink the coffee while the queue does its job. Pending is not an error state; it is a queue position with a countdown you can read yourself.

    Related jargon, defined

    Block
    A batch of confirmed transactions sealed with a hash and chained to its parent.
    Replace-by-fee
    Broadcasting a higher-fee duplicate to replace a stuck transaction in the queue.
    Base fee
    Ethereum's algorithmic price for block space, rising with congestion and falling with quiet.
    Fee rate
    The fee per unit of transaction size, which sets the queue position.
    Confirmation
    A block added on top of the one containing your transaction.
    TXID
    The transaction ID used to find a transfer on an explorer.

    Frequently asked questions

    Why is my crypto transaction stuck pending?+

    The fee you attached is below the going price for block space, so miners and validators pass it over. It sits in the mempool until it is picked up, replaced, or dropped.

    How long can a transaction stay in the mempool?+

    Hours to days on Bitcoin at a low fee rate, and most nodes eventually drop transactions that linger too long. Ethereum transactions wait until the base fee falls to their bid.

    Can I cancel a pending crypto transaction?+

    On Bitcoin, broadcast a higher-fee duplicate through replace-by-fee, which replaces the old version in node mempools. On Ethereum, wait for the base fee to fall or replace the transaction with a new one.

    Do Australian exchanges charge fees for pending deposits?+

    No. The only fee is the network fee you paid when sending, and pending means the chain has not confirmed the transfer yet.

    Does the mempool exist on every blockchain?+

    Every chain with an open fee market has one, including Bitcoin and Ethereum. Chains with fixed fees or scheduled finality still queue transactions, but the pricing works differently.

    Disclaimer: This information is general in nature and does not constitute financial or legal advice. Always consult a qualified professional for your specific situation.

    Keep learning

    Ivy Sinclair-Wren

    Ivy Sinclair-Wren

    Financial Chaos Analyst

    Connect on LinkedIn

    Ivy Sinclair-Wren is a Financial Chaos Analyst covering crypto markets, investing behaviour, and the Australian habit of checking prices during family dinners. Based in Melbourne, she reviews AUD Crypto Tracker's coin guides for accuracy, ATO alignment, and ruthless utility — no hype, no predictions, just what the data says.