A mempool is the set of valid, unconfirmed transactions a node has chosen to keep in memory. It is local. Your node has one. A miner has one. A public website advertising “the mempool” has one, or has a view of several. None of those is a protocol object the whole network shares.
Why two nodes disagree
A transaction spreads by gossip. A node that has not received it yet does not have it. A node that received it and then evicted it, because the pool was full or the fee was too low for that node’s policy, does not have it either. Bitcoin Core’s policy is not the consensus rules. Consensus decides which blocks are valid. Policy decides which unconfirmed transactions a node is willing to store and relay. Two honest nodes can apply different policies and hold different pools.
Replacement makes the divergence obvious. Under the replace-by-fee policy described in BIP 125, a node may drop a transaction in favor of a conflicting one that pays more. A node that does not apply that policy may keep the first. Until a block settles the conflict, both memories are real, and they disagree. Seeing a transaction on one explorer is evidence about that explorer’s peers. It is not evidence that every miner has it.
What “stuck” actually means
A transaction is stuck, in ordinary speech, when it has not been mined and the people you care about are not holding it. Broadcasting it again to nodes that will accept it is a different action from waiting for a global queue to move. There is no queue position the protocol owes you. Miners choose from the transactions they have, usually preferring higher fees per byte, subject to their own rules. A low-fee transaction can be absent from the pools that matter and still be sitting in yours.
The useful question is local. Which nodes have it, under which policy, and is there a conflicting spend? “The mempool” as a single place does not exist to answer that.
Fee websites inherit the same limit. An estimate is a view of the transactions a particular node, or a set of nodes, currently prefers to keep, translated into a guess about what miners will include. If your transaction never reached those nodes, the estimate does not describe your chances. If miners are running different policy from the node behind the website, the estimate describes the website. Broadcasting more widely, or looking at a miner’s own template when one is published, is a different measurement. It is still not a global queue. It is a larger sample of local ones.
Sources
- Bitcoin Developer Guide: peer-to-peer network.
- BIP 125, replace-by-fee.
- Bitcoin Core documentation, on mempool policy as distinct from consensus.




