ETH Price: $1,865.04 (-3.99%)

Block

#20051341
Block Height:
20051341
Status:
Finalized
Timestamp:
624 days ago (Jun-09-2024 02:39:35 AM +UTC)
Proposed On:
Block proposed on slot 9256396 , epoch 289262
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
Block Reward:
0.039546748300806643 ETH (0 + 0.100469663472102743 - 0.0609229151712961)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
65,410 bytes

Gas Used:
12,424,100 (41.41%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004903607921 ETH (4.903607921 Gwei)
Burnt Fees:
šŸ”„ 0.0609229151712961 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,706.00 / ETH
Hash:
0xdd31b3587dc1ec5a54c34232918ef4262a91dcd100c59c44d228323aea80dfd7
StateRoot:
0x23aaf810824ece7068c9cff5b6bf9330ff2f42635f6db133c92598e86d8cdbe8
WithdrawalsRoot:
0xd12552f9a76a096aca76b83badc346628e79d10cc343e6c9505e810ab6cb8096
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0x1b481e270e77e17d61c4e21683ef72b242b61e578a34d319864dfc2d7ff3f899
Parent Root Hash:
0x42203556c4b58343f75ffbde572dbb5b8dcadbfe75424705653f8c1a778d17bd
Beacon Chain Deposit Count:
1523759
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xc61891db3e2b84ff512218b000a8e18a4806f41cb5aa3e717c423e7546ac3b2b
Randao Reveal:
0x8f3f71332c55036bf8a1c93c8f72e9fb879f0ec4ace41902b80dea84b73a93ce17534a23bf0502a1e10f67afa9fbcae1088e1c6311bc9e324fe83bceb646ff85a199134a8283692e2ce8340cdc5aead288c8867164397ad7519ad649c5870c7a
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.04347293910207738 ETH
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:

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.