curl --request GET \
--url https://beacon-nd-422-757-666.p2pify.com/0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v1/beacon/blobs/{block_id}{
"data": [
{
"index": "<string>",
"blob": "<string>",
"kzg_commitment": "<string>",
"kzg_proof": "<string>",
"signed_block_header": {}
}
]
}curl --request GET \
--url https://beacon-nd-422-757-666.p2pify.com/0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v1/beacon/blobs/{block_id}{
"data": [
{
"index": "<string>",
"blob": "<string>",
"kzg_commitment": "<string>",
"kzg_proof": "<string>",
"signed_block_header": {}
}
]
}/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.
block_id — the block identifier to retrieve blobs for. This can be one of the following:
head — the head of the chaingenesis — the genesis blockfinalized — the most recent finalized block0x prefixdata — 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 blockkzg_commitment — the KZG commitment for the blobkzg_proof — the KZG proof for the blobsigned_block_header — the signed block header associated with the blobBlock identifier, e.g., 'head', 'genesis', 'finalized', or a specific slot number.
Was this page helpful?