Block
#18597561
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
843 days ago (Nov-18-2023 08:31:23 AM +UTC)
Transactions:
131 transactions and 65 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.033696502862499449 ETH (0 + 0.370053373843252259 - 0.33635687098075281)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
215,855 bytes
Gas Used:
15,993,378 (53.31%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000021031008645 ETH (21.031008645 Gwei)
Burnt Fees:
🔥 0.33635687098075281 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,963.67 / ETH
Hash:
0xbb7af10fae9fc6bebc46ef84d1387827806022215a5e7231c11490fdcf350f4d
StateRoot:
0x6e3c7a132fbee43ef7732144fefd34a48697eaae6e2debb54a28c91ec04cce14
WithdrawalsRoot:
0x520e3475a33a84c8a94e64cc22f1565fbc958abe2a59fd8cddd14407076a9542
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x547510d77a38a4f49ed77230377d9c9344eadbff43f2a65a53c57e4b27dcfb1a
Parent Root Hash:
0x3f2fc7863b583817ed5989c9e247275a9bd9ac3f5c04499eb51a8e74338766df
Beacon Chain Deposit Count:
1064198
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x8e42b24f16b06835c772678d2e780ade44292a01dfbbc50b814d5609efddb7e8
Randao Reveal:
0xb1df0162bf97d6153a906e33ba0ce54843599bc92d722019327e097a82aa8fd6b18ddfd760569a71b25d6ced11fee8f107d267222b39a32804f5b245396298482a3551ce4882b64a3ecc12bec3d9dec2d150665d8bda465bb1a7f80be03d9022
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.035063694869963384 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.