trace_block

Returns call traces for a block.

Erigon reference · All supported methods

Parameters

Parameters are positional, in the order below.

Parameter	Type	Required	Description
block	Block number or tag	Yes	Block whose call traces are requested.

Return value

An array of call traces. Each entry identifies the action, result or execution error, call path, and containing transaction/block where applicable.

Example

Replace <gateway-url> with your gateway base URL and <service-url> with the chain’s service path, such as service/ethereum.

curl -X POST "<gateway-url>/<service-url>" \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"trace_block","params":["latest"]}'

Illustrative response; values depend on the selected network and request:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": []
}

Direct behavior

The gateway selects providers supporting the requested tracing group and format. Unsupported formats are rejected rather than replaced.

The tracing group must cover the requested historical blocks or transactions. Providers may supply the result using retained trace indexes or replay; Direct checks the advertised coverage.

Limits

The shared limits cover the entire block and all its trace results. Internal reconstruction does not restart the deadline or create a new response allowance for each transaction. Genesis cannot be replayed because it has no parent execution state.

Reconstruction, internal splitting, and recovery share the gateway deadline; none gives the request an unlimited fresh budget.

For providers

Qualify for the entire applicable tracing group, including required formats and options. Historical combinations are verified separately; recent success alone does not establish historical coverage.

See provider qualification for checks and continued eligibility.