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

# Block by block_id

> Reference for the Block by block_id JSON-RPC method on the Chainstack blockchain via Chainstack nodes. Parameters, response, and examples included.

The `/eth/v2/beacon/blocks/{block_id}` method is a key API endpoint in the Ethereum Beacon Chain, designed to provide detailed information about a specific beacon block. This method is essential for developers and participants in the Ethereum network who need to access comprehensive data about a particular block, whether for analysis, verification, or development purposes.

<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

* `{block_id}`: This parameter specifies the identifier of the beacon block for which information is being requested. The block identifier can be a slot number, a block root, or a special value like 'genesis' or 'head'.

## Response

* `object` — beacon block information.
  * `root` — the root of the beacon block, a unique cryptographic hash that serves as an identifier for the block.
  * `slot` — the slot number at which the block was proposed. In the Ethereum Beacon Chain, slots are discrete time intervals at which new blocks can be proposed.
  * `proposer_index` — the index of the validator who proposed the block. This index identifies the specific validator within the Beacon Chain.
  * `parent_root` — the root of the parent block to which this block is connected, ensuring the continuity of the blockchain.
  * `state_root` — the root of the beacon chain state after the block's effect. This state root is crucial for verifying the integrity of the chain's state post-block.
  * `body` — the body of the block, containing transactions, attestations, and other relevant data. This includes detailed information about the block's operations and effects on the Beacon Chain.

The `/eth/v2/beacon/blocks/{block_id}` method is instrumental in providing a thorough understanding of individual blocks within the Ethereum network. It enables users to delve into the specifics of block structure, content, and the role each block plays in the broader context of the blockchain.


## OpenAPI

````yaml /openapi/ethereum_beacon_chain_api/state/getBeaconBlocksByBlockId.json GET /0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v2/beacon/blocks/{block_id}
openapi: 3.0.0
info:
  title: Ethereum Beacon Blocks API
  version: 1.0.0
servers:
  - url: https://beacon-nd-422-757-666.p2pify.com
security: []
paths:
  /0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v2/beacon/blocks/{block_id}:
    get:
      summary: Get beacon blocks by block_id
      operationId: getBeaconBlocksByBlockId
      parameters:
        - name: block_id
          in: path
          description: >-
            Block identifier, e.g., 'head', 'genesis', 'finalized', or a
            specific block root.
          required: true
          schema:
            type: string
            default: head
      responses:
        '200':
          description: Beacon block successfully retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BeaconBlockItem'
        '404':
          description: Beacon block not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    BeaconBlockItem:
      type: object
      properties:
        root:
          type: string
        block:
          $ref: '#/components/schemas/Block'
      required:
        - root
        - block
    Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
      required:
        - code
        - message
    Block:
      type: object
      properties:
        slot:
          type: integer
          format: int64
        parent_root:
          type: string
        state_root:
          type: string
        body:
          type: object
      required:
        - slot
        - parent_root
        - state_root
        - body

````