Status:
Finalized
Timestamp:
4 days ago (Jun-27-2024 12:51:23 AM +UTC)
Transactions:
191 transactions and 85 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.041812266846772634 ETH (0 + 0.096842032213828059 - 0.055029765367055425)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
87,782 bytes
Gas Used:
19,275,145 (64.25%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002854959865 ETH (2.854959865 Gwei)
Burnt Fees:
š„ 0.055029765367055425 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,445.80 / ETH
Hash:
0x02dae852f343fdce333854130bf5fc71c492a7577c7c84e2a2b44f940965e58e
StateRoot:
0x1da7c48e60fce205ff8353cea6f4a3b1f30a3e6f8f5eaf283a05cde4c4e45cc8
WithdrawalsRoot:
0x3be793e9bf3b72f3f5a9973fed03d042e8ef496b7b67543329294c7f957bd237
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2139d6ff417b9fa9493c8a3a1777f4f8b007cf5a2bacca8092d029b951f6fee3
Parent Root Hash:
0xe649a41baf7f74d17901e2deffc687e385a26b62180a2c48a5fe758b529f11d2
Beacon Chain Deposit Count:
1559878
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x19f8a01cef4489aae46ea89a19542618397ec7baeaab3cd088636e63286d96a5
Randao Reveal:
0xa66fd38148a774172982ec23351c70e632dcb5b3f90ef2d9c8857c9e35e6aa65083077b733499536bcff836cdf00caeb171fe3a93b1740cb81324cd8cc5c97fe5de6e544b34b58c8bba8f0b97219dd6d6c5d54166bd96e3909f7d0061f5e24b0
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.051125836031410096 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Blob As Calldata Gas:
10,399,492 (15.87 times more expensive)
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.