debug_traceBlockByNumber — Base JSON-RPC

Trace every transaction in a block.

Scope: base:rpc

Params schema

JSON

documented

[
  {
    "name": "block",
    "required": true,
    "schema": {
      "$ref": "#/components/schemas/BlockTag"
    }
  },
  {
    "name": "options",
    "required": false,
    "schema": {
      "$ref": "#/components/schemas/TraceOptions"
    }
  }
]

Result schema

JSON

OpenRPC

{
  "name": "traces",
  "schema": {
    "$ref": "#/components/schemas/TraceList"
  }
}

Parameter limits

JSON path	Frozen limit	Source
—	`unknown`	No numeric parameter ceiling is frozen; enforce the declared schema shape and deny an unknown oversized/range profile.

Historical block retrieval is not an archive-state guarantee. Selectors must be preserved; do not substitute pending, safe, or finalized with latest.

Rate limits and tier

These are enforced product-policy values, not measured upstream capacity or an SLA. Enterprise is finite, never physical “unlimited” capacity.

Tier	Limit / access	Category
Free	— (tier gated)	base_read_rpc_heavy
Basic	— (tier gated)	base_read_rpc_heavy
Pro	2 RPS sustained · up to 4 burst	base_read_rpc_heavy
Business	5 RPS sustained · up to 10 burst	base_read_rpc_heavy
Enterprise	5 RPS sustained · up to 10 burst	base_read_rpc_heavy

See Base limits and Burst capacity. The included buffer refills at sustained RPS; there is no quota on the number of bursts.

Errors

Code	Meaning here	Client action
`-32602`	Parameters fail the declared schema or upstream parser.	Fix the positional parameters; parser acceptance is not execution success.

Tier and budget rejections are not JSON-RPC errors: the gate decides them before the request reaches the RPC layer and answers with a plain HTTP envelope — 403 tier_insufficient (with an X-Required-Tier header) or 429 rate_limited (honor Retry-After). Both are enforced product policy, not measured capacity or an SLA.

Authentication/transport failures use the shared client error envelope. See Base errors.

Evidence

Fixture: missing — No complete successful correlated request/response pair.
Fixture registry: infra-4-sety/integration-base/research/R00/import/FIXTURES_INDEX.json.
Evidence boundary: no fixture-backed runtime claim is made.

Limitations

Availability is the frozen baseline, not deployed readiness. documented is the contract floor; evidence_kind retains unknown/source_summary.