Block
#22643080
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
125 days ago (Jun-06-2025 04:09:23 AM +UTC)
Transactions:
234 transactions and 271 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.023340073000804751 ETH (0 + 0.046789044055542551 - 0.0234489710547378)
Total Difficulty:
0
Size:
131,818 bytes
Gas Used:
29,782,220 (82.73%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.00000000078734799 ETH (0.78734799 Gwei)
Burnt Fees:
š„ 0.0234489710547378 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,478.31 / ETH
Hash:
0x8ef5252c35c5c287fb33aa38e25aec31074329f213680302882ebcf5d757533c
StateRoot:
0x851b204a10cb81c42dfc6a4c49a792fefb62bc86354aa018ba75773c3a773419
WithdrawalsRoot:
0xa30f37c2ddb4aa20f5bf70317c15f500e9c1238d8bebb1bbbdd3549bb1108aa9
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5cf2ec77bcbcebfa2464e69c06f7d8e7b3e8423a21b832334cd6d6701c619eaa
Parent Root Hash:
0x59f14069818b3e64d6964dc772a5afba163b2bf4261ce631ef0f46663855d53b
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0xdf22f62d1d8b7c227de9d14a9996fde36076c77d99dfc0d18a928ede765b8087
Randao Reveal:
0x98f9e6b63280d7853aaf35473d7dfca298c25ab5a0c09cb44e167dce10ae8dc4b24b6260c22dbb2c848d43534b1ccacf0932adf0d2fed5050886a244e49a2b4ec6a6d08f6387b403983ccf0ea0c09a2bc8f25485707b3e83d0f270108c75f3ef
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.019725200037368117 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
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.