> ## Documentation Index > Fetch the complete documentation index at: https://docs.beaconcha.in/llms.txt > Use this file to discover all available pages before exploring further. # Execution block overview > Retrieve one or more execution-layer blocks by block number. Provide block numbers as a comma-separated list in the `blockNumber` path segment (up to 100 values). The response includes per-block metadata, rewards, consensus linkage, and relay information when available. ## OpenAPI ````yaml /api/v1/bundled.yaml get /api/v1/execution/block/{blockNumber} openapi: 3.0.4 info: title: beaconcha.in API Documentation license: name: GPL-3.0 url: https://www.gnu.org/licenses/gpl-3.0.en.html description: >- > ⚠️ No new features or endpoints will be added to V1. We recommend the [V2 API](/api/overview) for all new projects. See the [migration guide](/api/v1-to-v2-migration). ## Introduction **Advanced and reliable API for accessing comprehensive Ethereum blockchain data.** - **Free Usage Policy:** The API is free to use under a fair use policy, with rate limits of 10 requests per minute per IP. - **Caching:** All responses are cached for 1 minute. - **Higher Usage Plans:** For higher usage plans, visit: [https://beaconcha.in/pricing](https://beaconcha.in/pricing). An API key is required to use these plans. ### API Key Usage API keys can be obtained at [/user/settings](https://beaconcha.in/user/settings) and must be included in requests either as a query string parameter or in the request header. #### Example: Query String Parameter ```bash curl https://beaconcha.in/api/v1/slot/1?apikey= ``` #### Example: Request Header ```bash curl -H 'apikey: ' https://beaconcha.in/api/v1/slot/1 ``` contact: {} version: '1.1' servers: - url: https://beaconcha.in description: Ethereum mainnet - url: https://hoodi.beaconcha.in description: Hoodi Ethereum testnet security: - ApiKeyAuthQuery: [] - ApiKeyAuthHeader: [] tags: - name: Epoch description: Data related to consensus layer epochs - name: Slots description: Data related to consensus layer slots - name: Validators description: Data related to consensus layer validators - name: Rewards description: Data related to validator rewards - name: Sync Committees description: Data related to sync committees - name: Rocketpool description: Data related to the rocketpool protocol - name: ETH.Store® description: Data related to the ETH.Store® metric - name: Validator deposits description: Data related to execution layer validator deposits - name: Blocks description: Data related to execution layer blocks - name: Gas description: Data related to gas prices - name: Address description: Data related to ethereum addresses - name: Network description: Network data - name: Misc description: Miscellaneous data - name: User description: User data - name: Machine Metrics description: Submit machine, beacon-node, and validator-client monitoring metrics paths: /api/v1/execution/block/{blockNumber}: get: tags: - Blocks summary: Execution block overview description: >- Retrieve one or more execution-layer blocks by block number. Provide block numbers as a comma-separated list in the `blockNumber` path segment (up to 100 values). The response includes per-block metadata, rewards, consensus linkage, and relay information when available. operationId: getExecutionBlocksByNumber parameters: - name: blockNumber in: path description: >- One or more execution block numbers as a comma-separated list. Each item must be a non-negative integer. A maximum of 100 block numbers is allowed per request. required: true style: simple explode: false schema: type: array items: type: integer minimum: 0 maxItems: 100 example: 17000000,17000001,17000002 responses: '200': description: >- Matching blocks were found. The `data` array contains one item per retrieved block. If a provided block number is not found, it is omitted from the result. content: application/json: schema: allOf: - $ref: '#/components/schemas/types.ApiResponse' - type: object properties: data: type: array items: $ref: '#/components/schemas/types.ExecutionBlockApiResponse' '400': description: >- The request is invalid (for example, malformed numbers or more than 100 values). content: application/json: schema: $ref: '#/components/schemas/types.ApiErrorResponse' examples: invalidBlockNumber: summary: Invalid block number value: status: 'ERROR: invalid block number' data: null tooManyBlockNumbers: summary: Too many values value: status: 'ERROR: only a maximum of 100 query parameters are allowed' data: null '500': description: An unexpected server error occurred while processing your request. content: application/json: schema: $ref: '#/components/schemas/types.ApiErrorResponse' examples: serverError: summary: Internal error value: status: 'ERROR: internal server error' data: null components: schemas: types.ApiResponse: type: object description: Standard success envelope used by all API endpoints. properties: status: type: string description: >- HTTP-independent status of the API operation. For successful responses this is always "OK". enum: - OK data: description: Response payload specific to the endpoint. nullable: true x-omitempty: true types.ExecutionBlockApiResponse: type: object description: >- Overview of an execution-layer block, including rewards, gas, parent links, and optional consensus/relay metadata. properties: blockHash: type: string description: 0x-prefixed 32-byte Keccak hash of the execution block. example: '0x160a5ea46dcbaca7fce7bbeef3a3448197c021af6c3e258150ab017629794678' blockNumber: type: integer description: Execution block number (>= 0). example: 23540530 timestamp: type: integer description: Block timestamp as Unix time in seconds (UTC). example: 1760017151 blockReward: type: integer description: >- Total block reward attributed to the block in wei (sum of priority fees and any MEV reward considered in this API). example: 15027635123493132 blockMevReward: type: integer description: >- MEV payment amount attributed to this block in wei; 0 when no relay/bribe data is recorded. example: 11268157891595494 producerReward: type: integer description: >- Reward paid to the fee recipient (coinbase) in wei. Equals blockMevReward when present; otherwise equals blockReward. example: 11268157891595494 feeRecipient: type: string description: >- Fee recipient (coinbase) address that received the block’s reward (0x-prefixed, 20-byte hex address). example: '0x4838b106fce9647bdf1e7877bf73ce8b0bad5f97' gasLimit: type: integer description: Gas limit set for the block. example: 44999957 gasUsed: type: integer description: Total gas used by all transactions in the block. example: 26436568 baseFee: type: integer description: EIP-1559 base fee per gas in wei. 0 for pre-London blocks. example: 473717334 txCount: type: integer description: Number of transactions included in the block. example: 235 internalTxCount: type: integer description: Number of internal transactions (traces) attributed to the block. example: 725 uncleCount: type: integer description: >- Number of ommers (uncles) referenced by the block. 0 for post-Merge PoS blocks. example: 0 parentHash: type: string description: 0x-prefixed 32-byte Keccak hash of the parent execution block. example: '0x57ddc629098d3a47ddf8c2a554c75c4d9ab0a8bd740c1e86b0f1da324a425953' uncleHash: type: string description: 0x-prefixed Keccak hash of the block’s ommers list (ommersHash). example: '0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347' difficulty: type: integer description: >- Difficulty field from the execution header. 0 for PoS blocks, non-zero for PoW blocks. example: 0 posConsensus: $ref: '#/components/schemas/types.ExecBlockProposer' description: Consensus-layer proposer linkage for this execution block. nullable: true relay: $ref: '#/components/schemas/types.RelayDataApiResponse' description: MEV relay metadata when the block was delivered via a relay. nullable: true consensusAlgorithm: type: string description: >- Consensus algorithm in effect for this block: "pos" for proof-of-stake (post-Merge) or "pow" for proof-of-work (pre-Merge). enum: - pos - pow example: pos types.ApiErrorResponse: type: object description: Standard error envelope returned when a request fails. properties: status: type: string description: >- Human-readable error indicator and message. The value begins with "ERROR:" followed by details. example: 'ERROR: ' data: type: string description: Optional additional context for the error. Null in most cases. nullable: true default: null types.ExecBlockProposer: type: object description: Consensus-layer proposer information for the execution block. properties: executionBlockNumber: type: integer description: Execution block number associated with this proposer record. example: 23540530 proposerIndex: type: integer description: >- Index of the beacon chain validator that proposed the corresponding block. example: 1843949 slot: type: integer description: Beacon slot at which the block was proposed. example: 12766094 epoch: type: integer description: Beacon epoch containing the proposer slot. example: 398940 finalized: type: boolean description: >- Indicates whether the epoch containing this block has been finalized on the consensus layer. example: false types.RelayDataApiResponse: type: object description: MEV relay metadata associated with an execution block built via a relay. properties: tag: type: string description: Identifier of the relay that delivered the block. example: ultrasound-relay builderPubkey: type: string description: >- 0x-prefixed hex-encoded public key of the block builder as reported by the relay. example: >- 0xa3523967a7955c0244910f23b7b1fc59636f03bec437286b622815408d51389f7f6cd54617733b93926b7860e1f6afb0 producerFeeRecipient: type: string description: >- Execution address designated to receive the builder’s fee (0x-prefixed, 20-byte hex address). example: '0xa27cef8af2b6575903b676e5644657fae96f491f' securitySchemes: ApiKeyAuthQuery: type: apiKey in: query name: apikey description: '' ApiKeyAuthHeader: type: apiKey in: header name: apikey description: '' ````