> ## 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. # Deposits by execution transaction hash > Retrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash. This endpoint returns every deposit log decoded from the transaction, including deposit amount, validator public key, withdrawal credentials, and signature verification status. ## OpenAPI ````yaml /api/v1/bundled.yaml get /api/v1/eth1deposit/{txhash} 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/eth1deposit/{txhash}: get: tags: - Validator deposits summary: Deposits by execution transaction hash description: >- Retrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash. This endpoint returns every deposit log decoded from the transaction, including deposit amount, validator public key, withdrawal credentials, and signature verification status. operationId: getEth1DepositsByTxHash parameters: - name: txhash in: path description: >- Execution-layer transaction hash to inspect. Provide tx hash as a 0x-prefixed hex string (64 hex characters after 0x). required: true style: simple explode: false schema: $ref: '#/components/schemas/primitives.EthTxHash' responses: '200': description: >- The transaction was found and any associated deposit events are returned in the `data` array. If the transaction contains no deposit events, the array is empty. content: application/json: schema: allOf: - $ref: '#/components/schemas/types.ApiResponse' - type: object properties: data: type: array items: $ref: '#/components/schemas/types.APIEth1TxDepositResponse' '400': description: >- The request is invalid (for example, a malformed or non-hex transaction hash). content: application/json: schema: $ref: '#/components/schemas/types.ApiErrorResponse' examples: invalidTxHash: summary: Invalid transaction hash value: status: 'ERROR: invalid tx hash parameter' 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: primitives.EthTxHash: type: string pattern: ^0x[a-fA-F0-9]{64}$ example: '0x3629639fe74ef981ff72ba2678130c700b779964e6c22fe42201445084e9d343' 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.APIEth1TxDepositResponse: type: object description: >- Details of a single validator deposit decoded from an execution-layer transaction. properties: amount: type: integer description: Deposited amount in gwei (1 gwei = 1e9 wei). example: 32000000000 block_number: type: integer description: Execution-layer block number that included the transaction. example: 23537869 block_ts: type: integer description: Block timestamp as Unix time in seconds (UTC). example: 1759985003 from_address: type: string description: >- Sender address funding the deposit (0x-prefixed, 20-byte hex Ethereum address). example: '0x26e8ce0d6c1424566ff8d584d1409b9fe651f27d' merkletree_index: type: string description: >- Merkle tree index of the deposit within the Ethereum deposit contract; 0x-prefixed hex-encoded uint64 as emitted in the DepositEvent log. example: '0xfab3220000000000' publickey: type: string description: >- BLS12-381 validator public key (48 bytes; 0x-prefixed hex with 96 hex characters). example: >- 0x8bcf64d7f36af7e4c642ff02bc8ecdef72593762538a86f6eeda6375d35302d4d307f9d2a11f2ff6c5483a5d1c8c81a1 removed: type: boolean description: >- True if the associated log was removed due to an execution chain reorganization. example: false signature: type: string description: >- BLS signature over the deposit message (96 bytes; 0x-prefixed hex with 192 hex characters). example: >- 0xb70208d62803c7695d8eb47fff79ac0273711191d0b1fc3b8bcaca649affba83b77cc8dad73cf5bfe2771918a1f767400bb0603e690294c9b8ffb73072f734cc8131e59b4ce4240aa8377dcd4388d1beaaea495b4b603432e83b46126d7575cb tx_hash: type: string description: >- Hash of the execution transaction that carried the deposit (0x-prefixed 32-byte hex). example: '0x5ddaf424a46ab378967ce45c72b8532386cbd558ddb3b5ddb8a828000ad57895' tx_index: type: integer description: Index of the transaction within its block (0-based). example: 90 tx_input: type: string description: >- Raw calldata of the transaction (0x-prefixed hex), containing the deposit payload for the DepositContract. example: '0x00' valid_signature: type: boolean description: >- Indicates whether the deposit signature is valid for the provided public key and deposit message. example: true withdrawal_credentials: type: string description: >- 32-byte withdrawal credentials (0x-prefixed hex). Usually starts with 0x01 for ETH1 address withdrawals or 0x00 for BLS withdrawals. example: '0x01000000000000000000000026e8ce0d6c1424566ff8d584d1409b9fe651f27d' 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 securitySchemes: ApiKeyAuthQuery: type: apiKey in: query name: apikey description: '' ApiKeyAuthHeader: type: apiKey in: header name: apikey description: '' ````