Skip to main content
The /eth/v1/beacon/blobs/{block_id} method retrieves information about blobs by block ID. This endpoint is crucial for accessing detailed data contained within blobs, including the slot, epoch, and the associated data. It enables developers and users to programmatically interact with and analyze the blob data associated with Ethereum’s beacon chain, which is especially useful in the context of rollups and data-intensive operations.
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

  • block_id — the block identifier to retrieve blobs for. This can be one of the following:
    • head — the head of the chain
    • genesis — the genesis block
    • finalized — the most recent finalized block
    • A slot number
    • A hex-encoded block root with 0x prefix

​
Response

The response is an object containing the following fields:
  • data — an array of blob objects, each containing:
    • blob — a hexadecimal string representing the actual blob data. This field provides the raw data that rollups or other Ethereum layer 2 solutions have submitted for inclusion in a block.
    • index — the index of the blob within the block
    • kzg_commitment — the KZG commitment for the blob
    • kzg_proof — the KZG proof for the blob
    • signed_block_header — the signed block header associated with the blob