Block
#18416928
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
855 days ago (Oct-24-2023 01:44:35 AM +UTC)
Transactions:
151 transactions and 40 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.058087339069189693 ETH (0 + 0.468023842024084064 - 0.409936502954894371)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
69,297 bytes
Gas Used:
12,484,231 (41.61%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000032836343941 ETH (32.836343941 Gwei)
Burnt Fees:
š„ 0.409936502954894371 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,785.20 / ETH
Hash:
0xd30774d08217639b661138eb7d7ca12fb93421d60892b51d0d9d02fcb163d1e1
StateRoot:
0xe17b4aa593d7f94f26e4d527c68a105a0a7840e22422d758d6b1bbcc813072e3
WithdrawalsRoot:
0xe9937e8ddb05e0b8d3a14643422703128ff23326e6d0c1a838d5c98881c510d6
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6bb5addc285e28d0c48aae19cc32609402138cec006a57a12aa2cb65b9db02cd
Parent Root Hash:
0x5e4a13fd33a27cac275ec907d960cf6e2a3bd749fe7d49d1d576d59f5806e85e
Beacon Chain Deposit Count:
1016138
Slot Graffiti:
Block by Stakely Lido016 (Hex:0x426c6f636b206279205374616b656c79204c69646f3031360000000000000000)
Block Randomness:
0x183b526823218a8d17b02ed782ad67a21f424064a76165f5f4327b7996c0cac8
Randao Reveal:
0xa5133c7a796f619b4e9cc53f2b7fa73fd29a74363d115a8d71e87c6e0d575fab968069ea1a5aed545c681648a4d0b19806198b0107a0350c7b02e0b62b933eed17eb99563e3d238300c0085f5e0060b63f9b2555dfc4ddc3e17e0bf90dc2e2aa
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.077093739204047652 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.