Status:
Finalized
Timestamp:
207 days ago (Jun-02-2024 05:23:59 AM +UTC)
Transactions:
138 transactions and 45 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.10825299979728205 ETH (0 + 0.15917401074843637 - 0.05092101095115432)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
53,177 bytes
Gas Used:
11,269,387 (37.56%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000451852536 ETH (4.51852536 Gwei)
Burnt Fees:
š„ 0.05092101095115432 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,779.06 / ETH
Hash:
0x8b0bdbd929268db98ee68a6dbabbcacb80a3129ec2fd2f8ab204780f56e0eff9
StateRoot:
0x457c7a7a06be4c2caeaa757235928b86b84cbfdc7568d79efa18c815bb55ebf0
WithdrawalsRoot:
0x987f91b8eec20459ea36f5b1e78c6318c645fa91feded9f4fb01f858b1dc5992
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x9b6aa63c59dcdb9619a8c69287921d32963ba5a6647a0ea2fddd77cf10cba045
Parent Root Hash:
0x4ba0499b8fa38f6354772ad0dbb43d51ac90436f476cd3aeb29861c4d064fa72
Beacon Chain Deposit Count:
1506492
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xbfc3abfd69a69022f635e6eb5d2689214a4c032982fbdc1c9af06b93c8419e15
Randao Reveal:
0x8a09942e43060dce465b8ded4348e8435e0b27d282fb13071e0084f3be433d0022a1f2bd7ad4db280c68d37fe9e6e730120413109230775da34ceddacd771a909db5bd982c779cd6c43b09ee7ca7712e03b724fe0f5cbc57030d1c56882c5dff
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.094961354039681202 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1.00 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
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.