Skip to main content
The mempool holds transactions that have been broadcast to the network but not yet confirmed in a block. Mempool data is real-time and changes frequently as transactions get picked up by miners.

Get all mempool transactions

Returns all pending transactions currently in the mempool.

Get mempool size

Returns the number of transactions currently waiting in the mempool.

Check if a transaction is in the mempool

You can check transaction status using the transactions endpoint, if type is MemPooled the transaction is pending.

Remove transactions from the mempool

Removes specific transactions from the local mempool. This does not broadcast a cancellation to the network, the transaction may still be picked up by other nodes.

Revalidate mempool transactions

Triggers the node to revalidate all transactions currently in the mempool against the current chain state.

A note on mempool data

Mempool contents vary between nodes. A transaction visible in your node’s mempool may not be visible in another node’s mempool until it propagates through the network. For the most reliable confirmation tracking, poll the transaction status endpoint until type is Confirmed. For production apps that need to track transaction confirmation, the recommended flow is:
  1. Submit the transaction and save the txId
  2. Poll /transactions/status?txId={id} every few seconds
  3. Once type is Confirmed and chainConfirmations is at least 1, treat the transaction as confirmed
  4. For high-value transactions wait for at least 110 confirmations