txpool_content
https://triport.io/rpc/bscReturn pending and queued transaction maps.
txpool_content returns the selected BNB Smart Chain node's pending and queued transaction maps.
Each top-level map is keyed by sender address and then nonce, with full transaction objects as values. Use it when an operator needs transaction-level txpool detail rather than aggregate counts.
Unlike txpool_inspect, this method returns transaction objects; unlike txpool_status, it returns the pool contents rather than two counters. It is observational only, and 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.pendingobjectresult.queuedobjectErrors
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_content",
"params": []
}),
});
const payload = await response.json();
console.log(payload.result);Notes
- The snapshot belongs to the selected upstream node and is not a canonical or pool-wide mempool view.
- The BSC categories use configured defaults of 15 / 20 / 100 / 250 RPS; they are marked unmeasured in the tier matrix.
- Related methods:
txpool_inspect,txpool_status,eth_getTransactionByHash.