JSON-RPC Method Reference

One page per capability: what each method does, an example request you can copy, and which chains actually serve it — measured, not claimed. Every cell below comes from the same weekly probe run that powers the method support matrix: real requests sent through the customer path (auth, routing, failover) against every EVM chain we serve.

Last probed 2026-09-13 · 54 EVM chains · served · ± some upstreams · unavailable

MethodWhat it doesChains serving it
eth_getBlockReceiptsAll receipts for a block in one call — the indexer's shortcut.50/54
eth_feeHistoryEIP-1559 base fees and priority-fee percentiles for fee estimation.51/54
eth_getProofEIP-1186 account/storage Merkle proofs, verifiable against the state root.46/54
eth_createAccessListEIP-2930 access-list generation via a dry-run of a transaction.43/54
debug_traceCallFull execution trace (opcodes, gas) for a call that is never mined.46/54
trace_blockParity-style internal-call traces for every transaction in a block.34/54
txpool_statusPending/queued counts from the node's mempool.33/54
trace_filterRange-scan of Parity traces — the workhorse of Safe-style indexers.9/54
trace_transactionFull internal-call tree for a single transaction.10/54
batchJSON-RPC batching — an array of calls in one HTTP request.53/54
archiveHistorical state queries pinned to old blocks via archive routing.45/54 (+2 partial)

Non-EVM chains (Solana, Cosmos family, Bitcoin family, and others) speak different RPC dialects — see their individual chain pages.