Status:
Finalized
Timestamp:
209 days ago (Jun-11-2024 05:07:35 AM +UTC)
Transactions:
252 transactions and 118 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.109377767916065159 ETH (0 + 0.256612003493048159 - 0.147234235576983)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
125,785 bytes
Gas Used:
28,032,146 (93.44%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.0000000052523355 ETH (5.2523355 Gwei)
Burnt Fees:
š„ 0.147234235576983 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,497.32 / ETH
Hash:
0x5f1b3cd3d58e1523d83530a68a3f089881cc2540c8c7408f68b071e9535a2105
StateRoot:
0xf57a4573ac8f047cee1e209b96485e6ed22e9953bad8918bdb388547e91e352e
WithdrawalsRoot:
0x6dd469942cf9e27f03eed4573ce00712460ceea221055594507cc8ee22c88b4e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x938604603cd4c7ecfbbe0a2f1e9310a3468ea0fe1c561818c9b86de8a4f04bb6
Parent Root Hash:
0x18a3b88621e747eee1c671644a50f142abfaf0acd81bab8a0d6e0b0ad3edb020
Beacon Chain Deposit Count:
1528231
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x23552a34a3e885e06a7e6f3ee44fbafd9c7dd1511923aea7836d3fb803c61930
Randao Reveal:
0xb4a737ba61eedf75f3388151bae452a20e94f6d90ca561dcf85ad7a241c767be5145ee092b1207f3af2f4ab173b018181607def9a29f5edfc957743e43fbf85bc413bea0c05aaec3f07e8d2094b6ec9181041922b0bd64f1995e8989c741d042
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.062783032892305836 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
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.