Block
#22625332
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
268 days ago (Jun-03-2025 04:30:59 PM +UTC)
Transactions:
270 transactions and 92 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.039509273825893368 ETH (0 + 0.19921121396047512 - 0.159701940134581752)
Total Difficulty:
0
Size:
97,287 bytes
Gas Used:
20,167,542 (56.02%)
Gas Limit:
35,999,930
Base Fee Per Gas:
0.000000007918760756 ETH (7.918760756 Gwei)
Burnt Fees:
🔥 0.159701940134581752 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,594.88 / ETH
Hash:
0x77b2f9720913adbe13aa34f9abe2283e17755436ea28a7c727788d57ead8a3dd
StateRoot:
0xedeb2f2b0ebed2b47447a8954966d5554b68484c3920ba2fc80ae9401be759d5
WithdrawalsRoot:
0x3a6b525d4c41802872058a61e5b0742d85d31f38aa97e1b89c99eb489ac63bfe
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x07a4d0effcd17b622751f6f31583ee509a6f0afee6a78254a744459431967c7b
Parent Root Hash:
0xde5ef627928753368d281309a45215f58ff9459f56c3583d1427c18e8a3b0e79
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xd7ee648772d80d52e8cb1b9d75fa6854706d6ccbf64239279862f435a615fd36
Randao Reveal:
0xaa9ead0479aa301d5afb4a6a993c6b1651312fd9c58e9b388cfe7155b8c33c5fd5b8c2919a43fe54702a687d566cda75016f92ef180c3892a005a6c334a0effc4bc5a9605d3ef75144bd6bef7d574939d5b02eded42b9a81f2505d6c8902a62a
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.03590098117638387 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (33.33%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000393216 ETH
Excess Blob Gas:
0 (0 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.