Retrieve blob sidecar by slot

The /eth/v1/beacon/blob_sidecars/{blob_sidecar_slot} method retrieves information about a specific blob sidecar by its root. This endpoint is crucial for accessing detailed data contained within a blob sidecar, including its slot, epoch, and the root hash of the blob sidecar itself. It enables developers and users to programmatically interact with and analyze the data blobs associated with Ethereum's beacon chain, which is especially useful in the context of rollups and data-intensive operations.

👍

Get your own node endpoint today

Start 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

• blob_sidecar_slot — the slot number of the blob sidecar to retrieve information about. This is a hexadecimal string beginning with 0x. The blob sidecar slot number acts as a unique identifier for each blob sidecar, allowing for precise queries and interaction with the beacon chain's data layer.

Response

The response is an object containing the following fields:

• data — a hexadecimal string representing the actual data contained within the blob sidecar. This field provides the raw data that rollups or other Ethereum layer 2 solutions have submitted for inclusion in a block.
• slot — an integer value indicating the slot number associated with the blob sidecar. The slot number helps contextualize the blob within the Ethereum protocol timeline.
• epoch — an integer value representing the epoch number related to the blob sidecar. This helps determine the blob's placement within the broader epoch-based structure of the Ethereum blockchain.
• blob_sidecar_root — a hexadecimal string that is the root hash of the blob sidecar, confirming the unique identifier used in the query.