Block
#17653468
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
969 days ago (Jul-09-2023 03:25:35 AM +UTC)
Transactions:
160 transactions and 118 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.160103076785833045 ETH (0 + 0.426153933182649835 - 0.26605085639681679)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
181,914 bytes
Gas Used:
19,346,365 (64.49%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000013751981646 ETH (13.751981646 Gwei)
Burnt Fees:
🔥 0.26605085639681679 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,863.11 / ETH
Hash:
0x3f0e402d78f040d085e3946e590a650fdf027e3f37ac98f24219690cc1eb2784
StateRoot:
0xc0ed3267c14de4dca9aab6d47b68a5512bf15bcc727c544b5ea75f7035532afa
WithdrawalsRoot:
0xe3156e749865252b62e93265e29244b006ce4981bb22d4bacdb2d2b067401eeb
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5ebd8fea745e98dc266ca767d0f3c3a5555cc19579356d9d56b4971458463cf6
Parent Root Hash:
0xa308e691730509a0a5df650458e2caae2e32d58167e5bc06bcb714e8e1010245
Beacon Chain Deposit Count:
844890
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3c42ceebb785d8cfe247137e5e877000f38204f375e54854e0cef66bdb4e60df
Randao Reveal:
0xac7e1092d1acabab07a8c8c587a9a1d7310e5e9610a3d3459e9163a8108e158db60b4aabfd7650ef014f2e88bd8b67e117d7be6d543ceb56ab17253e782e28e4813c30857c34d3ece35ce92f58c9f48c2a03ef21f158b9178cea704ac579ac90
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.160049006719658339 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.