Block
#22509083
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
282 days ago (May-18-2025 09:48:35 AM +UTC)
Transactions:
151 transactions and 94 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.01039362436935066 ETH (0 + 0.019064800806386304 - 0.008671176437035644)
Total Difficulty:
0
Size:
71,435 bytes
Gas Used:
15,014,916 (41.71%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000000577504159 ETH (0.577504159 Gwei)
Burnt Fees:
š„ 0.008671176437035644 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,498.72 / ETH
Hash:
0x884b5b496bdcc89aa46d83d800aceb772434ede97c59f2590286bc73f00bfab9
StateRoot:
0x24f1bec9f8a41d96dc07e684b18df7be91e775febb385f1f4a67d19ade582e66
WithdrawalsRoot:
0xae78fdc1a41e86258caed091c5aac7c7dd26da6130ab69e5a960e3fc907ee380
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb8dc80e04f403ab789bfa488c31bc5eb9d61134a58748ddcfb584fac68deb55f
Parent Root Hash:
0xd0529ef4f234971d1d277fe70822918b5517a57d939f57199664742c774a562d
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb22a51bbfe9f5eb9a134e19d5585b74cb73de00193a9498e741fd4afa84f1580
Randao Reveal:
0x8eececbf5472bd9e5fa8f8b954f67d1cc275d5bf401e52e5bd07f728610a84bbdf8a751dd62b5ea249ad204f5ab536fe19700216675946f30a002d6bad67f37a8f4d00055fb2379fd249b1ab54c2478b09e2c1c7a3c771cd2734495ef1fbed6c
Proposer Fee Recipient:
0x22eEC85ba6a5cD97eAd4728eA1c69e1D9c6fa778 (Fee Recipient: 0x22ee...778)
MEV Reward:
0.011419377319478601 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (66.67%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
262,144 (2 blobs)
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.