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-10-11 · 107 EVM chains · ✓ served · ± some upstreams · ✗ unavailable

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

Everyday methods, compared across chains

The methods every app calls, with what each chain actually returned: block times, extra fields, gas estimates, fee suggestions, error strings and which standard contracts are deployed.

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