Block
#0x2eda0ef0ed6484b6ab52d6f4499fb4e1fc27a5b0d41282cacb5c42626b925a35
Status:
Finalized
Timestamp:
281 days ago (Nov-15-2023 08:02:35 PM +UTC)
Transactions:
133 transactions and 45 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x777...C94 in 12 secs
Block Reward:
0.103251943611466225 ETH (0 + 0.631938893309951743 - 0.528686949698485518)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
42,751 bytes
Gas Used:
9,688,821 (32.30%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000054566695958 ETH (54.566695958 Gwei)
Burnt Fees:
š„ 0.528686949698485518 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$2,059.63 / ETH
Hash:
0x2eda0ef0ed6484b6ab52d6f4499fb4e1fc27a5b0d41282cacb5c42626b925a35
StateRoot:
0xff00af9475afb292334476b625adf4b8ad3a03515be65c6080cca7301070ae27
WithdrawalsRoot:
0xdbb910915d96b85e6c62a2123e68225e2b4fb534e89f9e2d441f89eb9c08ea64
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x553d228046c75f669b0a19eb804adcd3fa514fafa2b8eec996433c362999cbe7
Parent Root Hash:
0x4b27a429e380982fb3f61cea44f4e49865d36fe7de11e104b4613f279546a105
Beacon Chain Deposit Count:
1060544
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xdd1a962b9df55c5f1ce50db0f0f5c84da1316dfc2f656d3a504f502455cdf53a
Randao Reveal:
0xb71463f6563eb7fa0d72761243a558c7663d51c0ef35e46e665754b1b4805a73f7b18c88db7c331038ba9b0d26c27d8f04d73b1611eee25a48f28087642d90fcc83d56eca584e6d017a0308651c7d72b8039897010959a5516608330afc552a7
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.281726421779198368 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
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.