Status:
Finalized
Timestamp:
289 days ago (Apr-05-2024 10:09:47 AM +UTC)
Transactions:
162 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.017844416509290172 ETH (0 + 0.251914686758295643 - 0.234070270249005471)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
80,948 bytes
Gas Used:
14,796,403 (49.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000015819403557 ETH (15.819403557 Gwei)
Burnt Fees:
š„ 0.234070270249005471 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,319.12 / ETH
Hash:
0x856c6f2bc295f1d4ee3f9f4a7f6180201d7f512776af9fd5c816c7abdf004c30
StateRoot:
0x2ad0a0ab712266ac9afb34ac8dd40b3c3ed1edab9b4eace9dff0c35d13252b09
WithdrawalsRoot:
0x80a77524821eb6a9ff8accbf6079c1d1198bbd742db746cb45f965978814cd3d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x393190129cb67e23135a2f57f79006343880279217887db7b79296c59490b36f
Parent Root Hash:
0xb2c738add114bf3a4e77fe0509f4bf978ca53ece1487fde006f2817ceaba011d
Beacon Chain Deposit Count:
1410346
Slot Graffiti:
teku/v24.3.1 (Hex:0x74656b752f7632342e332e310000000000000000000000000000000000000000)
Block Randomness:
0x2d475f1b831edf096b6d4579ccc91c4e300aed57ed4e1109a146498a34426ce4
Randao Reveal:
0x85ae3dc12d319e9eb3821f8a97c5d8080acfd1b1ce9c9d6d54e72edc5c1271e1ed4cd9e6571ea1e2c9dd838b6c78875505d5a0bacbba149be894308d28edda8b939429acb94d80e6a3f710e89c33345704a48a419f58e199cc0b196abaf93e9b
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.020053285953604272 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5.00 Blobs (83.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Blocks are batches of transactions linked via cryptographic hashes. Any tampering of a block would invalidate all following blocks as all subsequent hashes would change. Learn more about this page in our Knowledge Base.