Block
#18655615
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
832 days ago (Nov-26-2023 11:40:59 AM +UTC)
Transactions:
329 transactions and 130 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.329017887482363772 ETH (0 + 0.862673549726154976 - 0.533655662243791204)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
144,510 bytes
Gas Used:
29,976,154 (99.92%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000017802672826 ETH (17.802672826 Gwei)
Burnt Fees:
🔥 0.533655662243791204 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$2,063.01 / ETH
Hash:
0x9a0fcbee2cf7ca8d83240d4a3964647bfce5274a64e8c437b2766838ee974411
StateRoot:
0x1841e87ceb709be0ba4d03f56d96747cc05abecdb209211166d34099e41bdd47
WithdrawalsRoot:
0x83db52eddcb129fb4f8d4b89ae548c2130e52de57fe38dd83549c9c1287d0352
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc841b72d4d1ea4cb7c24b45d48038293e61ed7f8510583b4c878cbb1f00b01b9
Parent Root Hash:
0x3d92ace60e4da85a6139250eea0099de6418198cf804d533b08a4a64de47af46
Beacon Chain Deposit Count:
1078401
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x98c4a0ab8ecdeafa2843094b722b5c5c2296606161e42272f1beb2dffc705aa0
Randao Reveal:
0x95e7ec9325cde5e62241f662290a6e66fe6968d5db46dbdaee221cf9e116a8add73f8084fdf9956bba1e7ba29448ba60153a3ca4ca321c1c8f21a5bf9d98065051f944b23ae02b2a451627c54a5fafc729fd1ab7cd5b6b79e1c573eaabb747e4
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
1.391304446927924884 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.