BNB Smart Chain
txpool_inspect
When BNB-funded transactions pile up on BNB Smart Chain during a busy PancakeSwap window, txpool_inspect lets you peer straight into the node's mempool. It belongs to the geth-family txpool namespace and returns a human-readable text summary of every pending and queued transaction the node is holding, organised first by sender address and then by nonce. Each entry collapses to a one-line string that names the recipient alongside the BNB value and gas terms. Call it at https://bsc.therpc.io/YOUR_API_KEY on chain ID 56 for an at-a-glance read on what is waiting to be mined versus what sits parked behind a nonce gap.
Use cases
- Track down a stuck BNB Smart Chain transaction by scanning the summary for its sender address and nonce to see whether it sits pending or queued behind a gap.
- Audit exactly what the mempool is holding during a high-congestion incident, reading off recipients and gas terms without parsing full transaction objects.
Parameters
This method takes no parameters. Pass an empty array [].
Response
| Type | Description |
|---|---|
| object | Object with `pending` and `queued` keys. Each is a map of sender address → nonce → human-readable string `"<to>: <value> wei + <gas> gas × <gasPrice> wei"`. |
Example request
Try it live in the BNB Smart Chain playground.
Errors & troubleshooting
| Code | Message | Cause |
|---|---|---|
-32601 | method not found | The node does not support the txpool namespace (e.g. non-Geth clients may omit it). |
Common pitfalls
- The method lives in the geth-family
txpoolnamespace, so nodes built on other client lineages may not expose it and will reject the call as unknown. - Its output is shaped for human eyes, not parsers; reach for
txpool_contentwhen you need structured, full transaction objects in code. - A heavily loaded BSC mempool can make the response enormous, so prefer
txpool_statuswhen all you want is a lightweight pending-versus-queued count.
Supported networks
- Mainnet — Chain ID: 56
- Testnet — Chain ID: 97