Block
#18254965
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
884 days ago (Oct-01-2023 10:02:47 AM +UTC)
Transactions:
100 transactions and 56 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.033860097498711668 ETH (0 + 0.136636108763723233 - 0.102776011265011565)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
272,444 bytes
Gas Used:
13,220,689 (44.07%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000007773877085 ETH (7.773877085 Gwei)
Burnt Fees:
🔥 0.102776011265011565 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,733.44 / ETH
Hash:
0x1d9045ec9e750e70c265e04ce7941fd5292f1f45a4f3f73049e9bce72d5197f2
StateRoot:
0x02b9926cad1b3c09095645cece5c0629cce24abe09de9f358da59fa204986cb9
WithdrawalsRoot:
0x54c445189e5281c01d42f332ef4076623172a97ac6c2acb4960b624ed288c427
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xee8c88a9a4558ccb5ef7630505c7b33c51f545d9cef82c38dfa7c5df27e87706
Parent Root Hash:
0x87aea6594f13b84b90a151255f9755aead22446cc4ddba589669b328694c4cfa
Beacon Chain Deposit Count:
982765
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x60e8b414b58cdd0eb8fce46a8fb4e9b265711f060a6affefc5a61707bcce40ed
Randao Reveal:
0x8577cd405abf9a94df27a835b48280806ef7d72458cd7c35cf5f95380ab84d333959eb3f60c14ccd4b34e9418c14f10c1876b9ac0cf8c2040b17888e0822a4f4b9b8d56edd410399773405921d51bc0f4cf5326949508b50f88e0fbdeb024a07
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.033898209302485233 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.