Block
#18779402
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
801 days ago (Dec-13-2023 07:43:35 PM +UTC)
Transactions:
160 transactions and 46 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.069445750913211024 ETH (0 + 1.079699411222405649 - 1.010253660309194625)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
175,596 bytes
Gas Used:
16,758,765 (55.86%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000060282106725 ETH (60.282106725 Gwei)
Burnt Fees:
š„ 1.010253660309194625 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$2,260.72 / ETH
Hash:
0xf887537cfe06602cab7d25486a1bd5719b6569b303a598b362a211090f146991
StateRoot:
0xff39f4e23825231ea0fa0c9636f607d3a5cfc14b20670c4d7bc4f9c7edd22af8
WithdrawalsRoot:
0x86f14574f600f728d31977c4e32fe8aa3e1b5a0bf65e395edb751b10f1c6de67
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb4a3090f9c9064455f253dacfc6e5f8e9e87893a9e04d9b63dabe131fc4ec201
Parent Root Hash:
0x9283b263194262ab309da387f3984c23a061878ceec9418e90a4268d68b28b0c
Beacon Chain Deposit Count:
1112043
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xc6a4dfa3a06a9b1a618696d13ca04ab18645f020cd238c66ed2364f38c0aa2c3
Randao Reveal:
0x8c073b5c8197054632254eaca2c2cd1e8e35cf9b0963ed6e9dffe686d5ed59965bcbf4b36b26dc209b9096dcb142da2d159c178119b3cc7960dc4fba61b866e67830bb5a668962d01ec5e216a4edce40da542ff189cda49e2a763ed3efa13f7f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.068212853251414549 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.