> ## 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/base-traceblockbynumber",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# debug_traceBlockByNumber | Base

The `debug_traceBlockByNumber` RPC method is used to retrieve detailed execution traces for all transactions included in a block, identified by the block's number. This method is particularly useful for developers and analysts who need to deeply understand transaction execution and state changes within a specific block.

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

## Request

To use `debug_traceBlockByNumber`, send a POST request with a JSON RPC call in the body.

## Parameters

* **Block Number** (`string`): The number of the block for which to retrieve the execution traces, in hexadecimal format.

## Response

The response includes detailed execution traces for all transactions in the specified block.

* **result** (`array`): An array of execution traces for each transaction in the block. Each trace provides comprehensive details about the execution, including calls, state changes, and gas usage.

## Use case

The `debug_traceBlockByNumber` method is essential for:

* Developers debugging complex interactions within a block.
* Analysts conducting forensic analysis of block transactions.
* Tools and services that provide insights into the Ethereum Virtual Machine (EVM) execution and state changes.


## OpenAPI

````yaml /openapi/base_node_api/debug_traceBlockByNumber.json POST /2fc1de7f08c0465f6a28e3c355e0cb14
openapi: 3.0.0
info:
  title: debug_traceBlockByNumber example
  version: 1.0.0
  description: >-
    This API example demonstrates how to use the debug_traceBlockByNumber method
    to retrieve detailed execution  traces for all transactions included in a
    block, identified by the block's number.
servers:
  - url: https://base-mainnet.core.chainstack.com
security: []
paths:
  /2fc1de7f08c0465f6a28e3c355e0cb14:
    post:
      tags:
        - Debug Operations
      summary: debug_traceBlockByNumber
      operationId: traceBlockByNumber
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - jsonrpc
                - method
                - id
                - params
              properties:
                jsonrpc:
                  type: string
                  default: '2.0'
                method:
                  type: string
                  default: debug_traceBlockByNumber
                id:
                  type: integer
                  default: 1
                params:
                  type: array
                  items:
                    type: string
                  default:
                    - '0xbb5583'
      responses:
        '200':
          description: >-
            Detailed execution traces for all transactions in the specified
            block
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                  id:
                    type: integer
                  result:
                    type: array
                    items:
                      type: object
                    description: >-
                      An array of execution traces for each transaction in the
                      block.

````