Block
#22844793
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
236 days ago (Jul-04-2025 08:54:47 AM +UTC)
Transactions:
357 transactions and 194 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.037058425900942776 ETH (0 + 0.057134338954554936 - 0.02007591305361216)
Total Difficulty:
0
Size:
190,288 bytes
Gas Used:
32,371,324 (89.92%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.00000000062017584 ETH (0.62017584 Gwei)
Burnt Fees:
š„ 0.02007591305361216 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,508.69 / ETH
Hash:
0xf5420bc0e27f90769beaafc3b54b6983e496d7c831ab1a2a2f96fb74f4580677
StateRoot:
0x46eb78264982da0405d553ae05d4f27cce93a0945fb0f84d44d7ed773765386e
WithdrawalsRoot:
0x18a3657415b2302a3abee9c0ab693462de4b9b6303a18ae7e78a2d007c972868
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x9fb033f4896efc7668d646d247174efe40724086fcc05ee626d7263f9897ed14
Parent Root Hash:
0xd1c407fa44e0856529ace18739850bff5b74dfe847c16e6b90f8c098bd416440
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x814bfdeccaaeabee0ec59933de28d35e4d2c725d138cc4ece757e49cd6cac6fe
Randao Reveal:
0xb9e54d38b11bdc24245fcbf051b9ea2c3d77206b006f13abc00883ea01a99c41ab8f07bb9682dd9a00e2ddde8655152c05581156f2f71c4b50fbc7261129e21c4783f0f2aad639dd55efa9ad071873945b4da51ed851d976037acd3ff5d86897
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.031229767833724598 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (55.56%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (55.56%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.00000000000065536 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.