Block
#20064809
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
647 days ago ()
Transactions:
125 transactions and 64 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.02242520752767145 ETH (0 + 0.104236401649159596 - 0.081811194121488146)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
53,822 bytes
Gas Used:
9,416,522 (31.39%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000008688047893 ETH (8.688047893 Gwei)
Burnt Fees:
🔥 0.081811194121488146 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,665.99 / ETH
Hash:
0xaaef059f142ee88f427f8b3f3d82a25e514788cae913aa723f7191589551dccb
StateRoot:
0x78095650491da56b4f8f1631ee3755865a00f9ca8e2eb48aa2815e4592c657f6
WithdrawalsRoot:
0x05bc64c76cffc225fdd6df5789979bb3ad2969e293948147dad002f4c8a7cd39
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7e72a956991d0b9e76bd8952021704f50d5801423a83db3b664b529fb4d0b288
Parent Root Hash:
0x35d6ca2d65eb4e27b2ee12c026ab9dcd6d427f7b1545e861b73c6ee801aed2df
Beacon Chain Deposit Count:
1527996
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xcb132a1e3e26f69f51829408454c444f83539afa72994e652552c6425f12cec0
Randao Reveal:
0x995d2373bc7b6afb9bf764ff2adbc10c8e9d055508bd3bb2653c1640c56018d93d1b29992deb82afada36ac4ef202a52048e9512257cc91d339463bd33912e697cbfccd2acda03936f1f94370f81e8a867db6d2a8387386f25fab3280242a169
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.07012163281122108 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
0 (0 blobs)
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.