Block
#18624469
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
830 days ago (Nov-22-2023 03:00:47 AM +UTC)
Transactions:
191 transactions and 101 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.302588689340494221 ETH (0 + 0.886945643293072436 - 0.584356953952578215)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
455,595 bytes
Gas Used:
19,849,051 (66.16%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000029440044965 ETH (29.440044965 Gwei)
Burnt Fees:
🔥 0.584356953952578215 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$2,064.08 / ETH
Hash:
0xb9fe6ed56ad63cf501ec277d3a96f927a9b870580e881ea4e6e35f33eb47146e
StateRoot:
0x38bc320224636b83cf81230fc16332257dbe2c06fd78722368983193822dd0e2
WithdrawalsRoot:
0x20862d0a9d11ba8be31c23b5ff24cdc2a60a3cdf9ad876fba402e1890d946490
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6c6df0e708bb2f899ce485b8a63e52ca38d69af3e9d3cf8df91e71085434d490
Parent Root Hash:
0xf69a54926bc8157e7f6fd1e5784fa8f21e2a2b50d4378ac6412b2e46dcdf8c1c
Beacon Chain Deposit Count:
1068987
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xecaf178c2881185593e528fb0bbf9350a89c4e91ffc6d26e1f721ed41a766144
Randao Reveal:
0x8ac0583816c77b4c8b61a23b7856977909345aa25391182e1fb492590cddee34faddc0e323595813caee3cbe5066dc7d00d17945ba6879ce6194a378f9c774c08d92d18af80e2570bfd71858581f90e451436d429fbe17b4c77c16566c6c3985
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.284989710826893507 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.