Block
#20117614
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
609 days ago (Jun-18-2024 08:59:47 AM +UTC)
Transactions:
143 transactions and 49 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.026647045327241169 ETH (0 + 0.117560312110459164 - 0.090913266783217995)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
138,983 bytes
Gas Used:
15,061,965 (50.21%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006035949943 ETH (6.035949943 Gwei)
Burnt Fees:
🔥 0.090913266783217995 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,482.27 / ETH
Hash:
0xb47506cee0bd5ed1309c24590833417c33752338399ca1607c860af32ea064f7
StateRoot:
0x0bcce1459eff3185610f94e2e670a52810c0674cae0c0f9e82a26a0b269794b9
WithdrawalsRoot:
0xe007951933efc4d4149b0fbceaedec8fe7f718e9b295d2cf9995bb85c99d110a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb928469cf0f0aeb21369403691fc50486e0fb9e12aed33b54f440415163c12d0
Parent Root Hash:
0x5f028a6eaeea28a7390136f6d45227d5c1ebd5f57b5cbdc3d2d9e135f7b8501d
Beacon Chain Deposit Count:
1542561
Slot Graffiti:
Nethermind for Lido TKcdcb (Hex:0x4e65746865726d696e6420666f72204c69646f20544b63646362000000000000)
Block Randomness:
0xcd1d7bd3f7304027ea6819cee39339e30283be1a4027df5e7cfd5a0337a47fc0
Randao Reveal:
0xa50e62fc32541d2352a239e1178a30010bb3bdd617f9abe25e06a6d1b7dc4de2a71a912f237dfe9f9a06c79e6327a0f916b15a0c19c22ef4a0c7ba37384b9415d7d44df861f1459eee859b86c6d5b3e42645850434f99def012ddf70fd32c19b
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.031435603122201945 ETH
MEV Payout Txn Hash:
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.