Block
#18482918
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
846 days ago (Nov-02-2023 07:28:47 AM +UTC)
Transactions:
113 transactions and 55 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.014728533291617541 ETH (0 + 0.226582196842288461 - 0.21185366355067092)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
49,804 bytes
Gas Used:
13,023,240 (43.41%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016267354633 ETH (16.267354633 Gwei)
Burnt Fees:
š„ 0.21185366355067092 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,801.34 / ETH
Hash:
0xfcedc8a637dddd238a1c717aee4ba37f0bde5e60a3695bc63a160f922588392e
StateRoot:
0x1b6f710bcf4485cdfbc8e42065a25ba45a48a03e1532ae0d51af091fcf5c3f9b
WithdrawalsRoot:
0x1d6670140e2e3469ad5890ab0ff2f30defb1f84e0130a8d2e3115a86cae87a6d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xaaf7ae9923c2bdedaca819c33e816927dffd38e51364a99ca3efb1a0b78b35b2
Parent Root Hash:
0x003079594775c2928f933531096c72d38d5912c65d9d6332353bd444634b2e27
Beacon Chain Deposit Count:
1031764
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x97b01c06179a8a8672833c33e114299cb2558beb96f9993060b73f5cfe5772f4
Randao Reveal:
0xa8bb53b9190bb6fa1e3e8d655968f3e4ebe49713805cd9a5ba591cc7fad22887f7e70f8d96087a5b90677c432325e7d60a4ced2b8a328e3066bfd65b541db8363a1fc09f2b3b96cdf9dfb2bfd8557a1ee2e0fff99981a2c727549a6e2e1004eb
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.014768845813327278 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.