Block
#18556950
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
837 days ago (Nov-12-2023 04:13:47 PM +UTC)
Transactions:
138 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.067461209005877692 ETH (0 + 0.545480391537698248 - 0.478019182531820556)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
96,586 bytes
Gas Used:
10,658,252 (35.53%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000044849679153 ETH (44.849679153 Gwei)
Burnt Fees:
🔥 0.478019182531820556 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$2,045.40 / ETH
Hash:
0xc6f0cf5207a444a59834c34204fd61f64027d90c348dcfff96b7012dc1f2ff45
StateRoot:
0xebd724cf4638f7ca799f25bc28e2245c4a39796de688ed594a57089b686741c3
WithdrawalsRoot:
0x82fe8791f8ca6ca95198b21e665ef1879051300eed8e1a5732f45e5b9b0a8ea4
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x635a16f3c4d0495aa06f0f81f8a8e316c0706037cd9d64da434b0528b0342c4a
Parent Root Hash:
0xbaa7ffd96697b707de8fbfc32c5a9b563f98728f769e6d8bbdda181484006812
Beacon Chain Deposit Count:
1054958
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xad9b413f957ee9102342c3c4c715327913a17bbb0c85acf89d32a4b0c2ea4932
Randao Reveal:
0xa6b4dcb562430f72000944c03157c85cb7970e6b49559aebaa6c4ca1df313db32221763ea378e86c5d9792748e592d02133e160b0441f2afd676ccfad377a6e714d9f74f60199ca985ad1f904d75b3dac499588e3faab70cb26a3a5e960869dc
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.06942036399257476 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.