debug_traceBlockByNumber
Hyperliquid node API
debug_traceBlockByNumber | Hyperliquid
The debug_traceBlockByNumber method returns detailed trace information for all transactions in a specific block identified by block number.
POST
debug_traceBlockByNumber
Documentation Index
Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
Use this file to discover all available pages before exploring further.
This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see Hyperliquid methods for the full availability breakdown.
debug_traceBlockByNumber method returns detailed trace information for all transactions in a specific block identified by block number. This method provides comprehensive debugging information including call traces, gas usage, and execution details for each transaction.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
blockNumber(string, required) — The block number in hexadecimal format (e.g.,"0x1"), or one of the tags:"latest","earliest","pending".tracerConfig(object, optional) — Tracer configuration:tracer(string) — Tracer type ("callTracer"or"prestateTracer").
Response
The response is an array of trace objects, one per transaction in the block. WithcallTracer, each trace contains:
type(string) — Call type (e.g.,"CALL","DELEGATECALL").from(string) — Sender address.to(string) — Recipient address.value(string) — Value transferred in wei (hex).gas(string) — Gas provided (hex).gasUsed(string) — Gas used (hex).input(string) — Call input data.output(string) — Call output data.
Example request
Shell
Example response
Use case
Thedebug_traceBlockByNumber method is useful for:
- Debugging all transactions in a specific block by number
- Analyzing gas usage patterns across block transactions
- Tracing internal calls and value transfers within a block
- Building block explorers with detailed execution traces
Body
application/json
Last modified on May 18, 2026