debug_traceCall on BNB Smart Chain
Measured 2026-10-04 by our weekly probe, which calls debug_traceCall through the same BNB Smart Chain endpoint customers use.
What debug_traceCall does
Executes a call against a block's state and returns its execution trace (with a tracer such as callTracer), without sending a transaction. It is the standard way to see what a call would do internally before you submit it.
debug_traceCall on BNB Smart Chain: what we measured
- Default BNB Smart Chain routing keeps state for roughly the last 64 blocks (about 29 seconds of BNB Smart Chain history). Tracing against a block older than that needs historical state. Archive routing did not measure as available on this chain.
Example request
curl -s https://rpc.swiftnodes.io/rpc/bsc?key=YOUR_API_KEY \
-X POST -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"debug_traceCall","params":[{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{"tracer":"callTracer"}]}'import { createPublicClient, http } from "viem";
const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/bsc?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: debug_traceCall on BNB Smart Chain
const result = await client.request({
method: "debug_traceCall",
params: [{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{"tracer":"callTracer"}],
});Other methods on BNB Smart Chain
- eth_getLogsSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- trace_blockSupported
- trace_transactionNot available
debug_traceCall on other chains
Support differs by chain; the full measured table is on the debug_traceCall reference.
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Sonic
- Linea
- Scroll
- zkSync Era
- Blast
- Mantle
- Gnosis
- Celo
- Berachain
- Monad
- Unichain
- Kaia
- PulseChain
Frequently asked questions
Does BNB Smart Chain support debug_traceCall?
Yes. debug_traceCall answered correctly on the SwiftNodes BNB Smart Chain endpoint in our weekly method probe (2026-10-04), which sends real requests through the customer path.
Are there limits on debug_traceCall on BNB Smart Chain?
Default BNB Smart Chain routing keeps state for roughly the last 64 blocks (about 29 seconds of BNB Smart Chain history). Tracing against a block older than that needs historical state. Archive routing did not measure as available on this chain.
BNB Smart Chain endpoints, live block height and WebSocket status are on the BNB Smart Chain RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.