Mempool (transaction pool)
Last updated:
Applies to: EVM chains
In more detail
Each node keeps its own pool, so there is no single global mempool: two nodes can hold different transactions at the same moment. EVM clients such as Geth split the pool into pending transactions, which are executable now, and queued transactions, whose nonce is ahead of the sender's next one.
Nodes that expose the txpool namespace answer txpool_status (counts), txpool_content (full transactions) and txpool_inspect (summaries). Not every chain has one: Solana's documentation states that it has no concept of a mempool — an RPC node forwards a submitted transaction to the current and next leaders instead.