Start with the node and snapshot

A mempool is the set of unconfirmed transactions a node currently retains. Nodes receive transactions at different times and can apply different acceptance and eviction policies. When comparing figures from two explorers, record the time and the source. A difference does not by itself imply that either node is broken.

Compare demand in virtual bytes

Bitcoin Core’s getmempoolinfo distinguishes transaction count, total virtual size and dynamic memory use. Comparing count alone treats one small payment and a transaction with many inputs or outputs as equal. Use total virtual size to assess the volume of block space being bid for, and memory use when you are investigating the node’s own resource limits.

Look at fee bands and dependencies

For a transaction estimated at a given sat/vB rate, inspect the volume of transactions in higher fee bands before interpreting the total backlog. An unconfirmed parent and its child can be evaluated together, and miners can use different selection policies. The fee chart is a snapshot of local conditions. Future arrivals and the time to the next block can change the outcome.

Separate the node floor from a confirmation estimate

The mempool’s reported minimum fee is about the node accepting or retaining a transaction under its policy. A confirmation estimate addresses competition for block space over a target number of blocks. A transaction can clear the node’s threshold and still wait through several blocks.

Sources

  1. Bitcoin Core RPC · getmempoolinfo
  2. Bitcoin Developer Guide · Transactions

Prepared with AI assistance. This guide explains protocol behavior for educational use.

Editorial policy (Chinese)