Block
#22679503
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
258 days ago (Jun-11-2025 06:22:59 AM +UTC)
Transactions:
210 transactions and 86 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.034850307876345186 ETH (0 + 0.092430305506797063 - 0.057579997630451877)
Total Difficulty:
0
Size:
82,496 bytes
Gas Used:
35,958,951 (99.98%)
Gas Limit:
35,964,810
Base Fee Per Gas:
0.000000001601270227 ETH (1.601270227 Gwei)
Burnt Fees:
š„ 0.057579997630451877 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,772.57 / ETH
Hash:
0x7e3ff5102d643b868f45794c53a575b89fef618f30b93264ee1a8f181bb43a7f
StateRoot:
0x79df7efc55c17ad288980e87ce4e96efcd705f9b5bdd1dbcb8ff1ceadedab864
WithdrawalsRoot:
0x0d9ff0f8dddab7e788a47c91870bece15f53f4111eb94cb9ceb630fca01f3bac
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8b9b9947b7bc7e537225b40f0be5aeef8299123d7cdb4489a0f9cee9048edae6
Parent Root Hash:
0xc2b62198f2ffe8f4111214a0b52c057358e90b644a3f989723db0afb002d772f
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x83271fb077ea8bc2eb76882d871ec3864ddcc2ae20c96be6c062c47b99b12f9a
Randao Reveal:
0x95fab91e3386eeeadb9d168c743f86c2edc2592b00761a72936719e8659dfbe8c4a52ad92a16729afbcd9882006382aa10d70554ca5a32b1b74b9ba566032d8062c4d1d9c5c9fa1afb1ce2be4e125973447945afeec4afffdc5cfb14612fa5f9
Proposer Fee Recipient:
0x60Ac32d416507c844b43E29B2e12DD23f5277420 (Fee Recipient: 0x60ac...420)
MEV Reward:
0.033966459107002128 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:
131,072 (1 blob)
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.