Docs · method · EVM

debug_traceBlockByHash

Units per call2 (heavy)
Cachenever
RuleHeavy (2 units). Served from supply with the debug API; availability differs per chain and is measured, not promised — on a chain without it the call answers -32601 with the concierge path.
ChainsEthereum Mainnet · Base Mainnet · Arbitrum One · OP Mainnet · Polygon PoS
Specificationhttps://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug

Example

curl -s https://flexyield.io/rpc/eth_mainnet \
  -H "Authorization: Bearer $FLEXYIELD_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"debug_traceBlockByHash","params":["0x<hash or block>",{"tracer":"callTracer"}]}'

When the rule applies — the exact answer

HTTP 404, JSON-RPC code -32601. The body says what to do next and carries a request id you can file as a ticket.

{
  "error": {
    "code": -32601,
    "message": "debug_traceBlockByHash isn't served on this chain yet — tell us what you're building and we'll enable or tailor it for your project, usually within a day: hello@flexyield.io",
    "data": {
      "contact": "hello@flexyield.io",
      "docs": "https://flexyield.io/docs",
      "request_id": "<uuid>",
      "support": "/support/new?request_id=<uuid>"
    }
  }
}

Questions

How many units does debug_traceBlockByHash cost?

2 units per call (heavy class).

Is debug_traceBlockByHash available on every chain?

No — it depends on the debug API behind the chain; the status of each chain's supply is measured continuously.

All methods: methods and limits · docs · AI agents: the same call is the rpc_call MCP tool.