Block
#18180712
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
903 days ago (Sep-21-2023 12:34:11 AM +UTC)
Transactions:
170 transactions and 91 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.072955352948923734 ETH (0 + 0.234856087222408282 - 0.161900734273484548)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
272,814 bytes
Gas Used:
17,942,747 (59.81%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000009023185484 ETH (9.023185484 Gwei)
Burnt Fees:
🔥 0.161900734273484548 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,584.04 / ETH
Hash:
0x3a76e9de9752238e694045e6a5fb99a3eefb7c89a8d7e3f6784f3aac17d1f2a3
StateRoot:
0xd7fb13334660a502d4080a901fdd6532b697031cfab25abdb108fe849997e85c
WithdrawalsRoot:
0xdab41bb951606c5684ba9179327e17f95a8b3adbea05100454fec4f58f97f41a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xa0378f9ec30d00b80faca1904271e31ac5df15b1ae8562dcc9a081901e2540eb
Parent Root Hash:
0x404334350e0cbfd1314909c8398366e8742076918ea0ba716171fcbf0cf2ccde
Beacon Chain Deposit Count:
968875
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x4843ce211b5e608c7796d257b483415edb6d254d910b37f48140a7621bed8c40
Randao Reveal:
0x85a183518d65388a0b8055b330cc0420e4258c36fcd9f07dc0fb1da5cfeec855b62260b9e11b89a157ed4d031b93d97002451fde44e484f8c5a6a2059b794e1c768510a1e68c80bea45ca783a74982b7714ac74368f7d33575faed5a5ab868e5
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.065566381009705106 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.