Skip to main content
Mempool configurations vary wildly across different protocols & node client configurations. The table here is a maintained reference of mempool configurations & specifics across all the protocols that Chainstack supports.
On protocols with no public mempool, pending-transaction methods like eth_newPendingTransactionFilter and eth_subscribe("newPendingTransactions") return empty by design — pending transactions are visible only to the sequencer. On Base and Optimism, follow transactions in real time with Flashblocks instead — see the how-to guides (Base, Optimism) or how Flashblocks works (Base, Optimism).
The table structure:
  • Protocol — protocol name.
  • Protocol availability — details of the mempool availability on the protocol level.
  • Chainstack availability — how to access the protocol’s mempool on Chainstack.
  • Client configuration — the default node client configuration for the mempool as deployed at Chainstack.
  • Example — a simple curl example. Remember to replace YOUR_CHAINSTACK_NODE with your Chainstack node endpoint for that particular protocol.
Remember that whatever the default configuration, we can always customize it for you on a dedicated node .

Ethereum txpool_content

Polygon txpool_content

BSC txpool_content

Gnosis txpool_content

Filecoin MpoolPending

Fantom txpool_content

Tezos pending_operations

Bitcoin getrawmempool

Ake

Ake Director of Developer Experience @ Chainstack
Talk to me all things Web3
20 years in technology | 8+ years in Web3 full time years experience
Last modified on July 9, 2026