> ## 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.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.chainstack.com/feedback

```json
{
  "path": "/reference/hyperliquid-evm-debug-trace-block-by-number",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# debug_traceBlockByNumber | Hyperliquid

> Returns detailed trace information for all transactions in a specific block identified by block number. This method provides comprehensive debugging information for an entire block, including call traces, gas usage, and execution details for each transaction.

<Info>
  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](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

The `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.

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## 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. With `callTracer`, 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 Shell theme={"system"}
curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "debug_traceBlockByNumber", "params": ["0x1", {"tracer": "callTracer"}], "id": 1}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm
```

## Example response

```json theme={"system"}
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": []
}
```

## Use case

The `debug_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


## OpenAPI

````yaml /openapi/hyperliquid_node_api/evm_debug_trace_block_by_number.json post /evm
openapi: 3.0.0
info:
  title: Hyperliquid EVM API - debug_traceBlockByNumber
  version: 1.0.0
servers:
  - url: >-
      https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
  /evm:
    post:
      summary: debug_traceBlockByNumber
      description: >-
        Returns detailed trace information for all transactions in a specific
        block identified by block number. This method provides comprehensive
        debugging information for an entire block, including call traces, gas
        usage, and execution details for each transaction.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - jsonrpc
                - method
                - params
                - id
              properties:
                jsonrpc:
                  type: string
                  enum:
                    - '2.0'
                  default: '2.0'
                  description: JSON-RPC version
                method:
                  type: string
                  enum:
                    - debug_traceBlockByNumber
                  default: debug_traceBlockByNumber
                  description: The RPC method name
                params:
                  type: array
                  description: Method parameters
                  default:
                    - '0x1'
                    - tracer: callTracer
                id:
                  type: integer
                  default: 1
                  description: Request identifier
            example:
              jsonrpc: '2.0'
              method: debug_traceBlockByNumber
              params:
                - '0x1'
                - tracer: callTracer
              id: 1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                  id:
                    type: integer
                  result:
                    type: array
                    description: Trace results

````