txpool_status
https://triport.io/rpc/bscReturn pending and queued transaction counts.
txpool_status returns pending and queued transaction counts from the selected BNB Smart Chain node's txpool.
Both counters are EVM hex quantities. Use it for a lightweight txpool size signal when individual pending transactions are not required.
Use txpool_content for full transaction objects or txpool_inspect for compact entry summaries. The view is observational and node-local; Triport does not expose BSC transaction submission.
Parameters
JSON-RPC params must be an empty array: [].
Response
The response below is the checked fixture for this method; it is reproduced without changing its fields or values.
resultobjectresult.pendingstringresult.queuedstringErrors
Errors use the standard JSON-RPC error envelope. See BSC errors for network-specific classification and the linked shared reference.
| Code | Meaning | When it happens |
|---|---|---|
-32602 | Invalid params | A required positional parameter is missing or a value does not match the OpenRPC schema. |
401 | Unauthorized | The x-token API key is missing or invalid. |
429 | Rate limited | The request exceeds the configured category RPS for the caller's tier. |
Examples
JavaScript (fetch)
const response = await fetch("https://triport.io/rpc/bsc", {
method: "POST",
headers: {
"x-token": process.env.TRIPORT_API_KEY,
"Content-Type": "application/json",
},
body: JSON.stringify({
"jsonrpc": "2.0",
"id": 1,
"method": "txpool_status",
"params": []
}),
});
const payload = await response.json();
console.log(payload.result);Notes
- The counters belong to the selected upstream node and are not a canonical or pool-wide mempool total.
- The BSC categories use configured defaults of 15 / 20 / 100 / 250 RPS; they are marked unmeasured in the tier matrix.
- Related methods:
txpool_content,txpool_inspect,eth_getTransactionCount.