Block
#22567301
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
274 days ago (May-26-2025 01:36:11 PM +UTC)
Transactions:
142 transactions and 73 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0xd87f...d96 in 12 secs
Block Reward:
0.00923436078045526 ETH (0 + 0.027313245277291192 - 0.018078884496835932)
Total Difficulty:
0
Size:
58,498 bytes
Gas Used:
11,622,876 (32.29%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000001555457057 ETH (1.555457057 Gwei)
Burnt Fees:
š„ 0.018078884496835932 ETH
Extra Data:
bobTheBuilder.xyz (Hex:0x626f625468654275696c6465722e78797a)
Ether Price:
$2,564.47 / ETH
Hash:
0xc0ec3ff96c52e41374737c1dc738bc2e3173470765ca5547e6b32e4ff00a44e3
StateRoot:
0x4fa871dd208338327e792b9ebb77c844fd14244a0d1250e3d2b09fddfaddc196
WithdrawalsRoot:
0xd75198123010930f5f80fed5329e3a85d00bbfe0ac942528551ffc25b2a8280f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7e47d213535212dac4ef2299029613068e9da7ca64ebffb046dc3db07684a5b3
Parent Root Hash:
0xfc8940bfa7976ddd2c0c92c7f1e8f626af88f7069132f767290cb3d0b2b33b9d
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x87a14090b7d319f64827de86849909f4a85b0e6fb824a949ac550fed2d3756a1
Randao Reveal:
0xb8b7b7fbe5cc5135cac537efeb67e12ae0212f4cf7f184c22aa58ffbf4f17bf3691e19bfb30aeb7085ed480329d523e90e058dfe272ffea001c35e37c61a490c0fae58a9de71df8281c9d929b7e7ca7c98eee4411e2e083b6a903c8ae5c60659
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.082890702446165812 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.