txpool_status

txpool_status returns the number of pending and queued transactions in an Avalanche C-Chain node's transaction pool, as two hex-encoded integers. Pending transactions are ready for inclusion in the next block; queued ones are waiting on a nonce gap or other condition. It is the lightweight counterpart to txpool_inspect — just the totals, no per-transaction detail — which makes it ideal for cheap, frequent polling of mempool depth. On the C-Chain, the EVM chain where AVAX pays for gas under Snowman/Avalanche consensus, these counts give a quick read on congestion. Send the request to https://avalanche.therpc.io/YOUR_API_KEY (chain ID 43114, 0xa86a).

Use cases

• Poll mempool depth on the C-Chain to detect congestion and raise the gas price on outgoing AVAX transactions when the pending count climbs.
• Feed a dashboard gauge that shows the current C-Chain transaction backlog at a glance, using the pending and queued counts as a real-time congestion signal.

Parameters

Este método no acepta parámetros. Pasa un array vacío [].

Response

Example request

1curl https://avalanche.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "txpool_status",
7    "params": [],
8    "id": 1
9  }'

Try it live in the Avalanche playground.

Errors & troubleshooting

Common pitfalls

• The txpool namespace is Geth-style. Avalanche C-Chain's coreth client is Geth-derived, but not every endpoint enables it, so a node without the namespace returns "method not found".
• The counts are instantaneous snapshots that shift quickly as the C-Chain produces blocks every one to two seconds. Do not cache them aggressively — re-poll when you need a current reading.

Supported networks

• Mainnet — Chain ID: 43114
• Fuji

See also

• txpool_inspect

1curl https://avalanche.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"txpool_status","params":[]}'