Block
#18605607
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
827 days ago (Nov-19-2023 11:37:47 AM +UTC)
Transactions:
149 transactions and 70 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.052321804499456812 ETH (0 + 0.352217766013321612 - 0.2998959615138648)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
165,136 bytes
Gas Used:
18,355,720 (61.19%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000001633801134 ETH (16.33801134 Gwei)
Burnt Fees:
š„ 0.2998959615138648 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,012.46 / ETH
Hash:
0xdf7feaff24e9773c937bfa0497f79de31b6ecce3df942e8ee7c988f6e6dcd4cf
StateRoot:
0xe09ab486ca66f9e7b9e7797cf07cc7f8de72aa0967463eb6e5ef1a85e98e3c3f
WithdrawalsRoot:
0x764f10513ddc5d4ee57d8c4a223b86a2f7c23c7c9afe1a85fde1cd0c34d6a558
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1f264e7003f51d6cd7a7350f20b7a24e008a8c7a5dfbc6c135ca9ebe5e80f64a
Parent Root Hash:
0xe949616d51219eb73e3e8284f2d3ff66a0b398d9fab20bb183d37d51bf470fc6
Beacon Chain Deposit Count:
1065260
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x5c478169185380cb2313df99bd55b0a5f2899e22c2c40c51a33309beebaf28de
Randao Reveal:
0x9661fa9ba7c9811cd42d7ef66c2244d2e0aaffc568f1668920412efcdf6ff8ea140a8563ea4e81bd40323bc2b45023ca0007ece47e2e3a796dd8cb83a4235f11687083f87de2644e40e6fdce50fe5f9ec2bc9c7e22283341bc142a2384147c5a
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.055243323451996452 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.