Block
#22516372
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
279 days ago (May-19-2025 10:18:59 AM +UTC)
Transactions:
202 transactions and 74 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.018573384907212299 ETH (0 + 0.030518926479246083 - 0.011945541572033784)
Total Difficulty:
0
Size:
71,012 bytes
Gas Used:
14,546,402 (40.49%)
Gas Limit:
35,929,656
Base Fee Per Gas:
0.000000000821202492 ETH (0.821202492 Gwei)
Burnt Fees:
š„ 0.011945541572033784 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,528.66 / ETH
Hash:
0x572bdf71bdd97c54d13fbee346537af54f411a5cd48ab18c455d3ad594bd2e4b
StateRoot:
0xd2808ca0b21e58e4f1cf213a98a16ad43a99e0f11f58acb2531d55f005b79d1e
WithdrawalsRoot:
0x197befd500f890d7763ccf77f6757410926d3305b21a61e9067e1505b973a91c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1141fb94dd53b010e6935ab6ad811df29f61cf9becfac05efec6fd4133651bc3
Parent Root Hash:
0x271a55a6fc6c6efb36a88fcf55746b462a5893ca26b3831c0abceb48747d6613
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x6b2939899970c3e1ca3773a1ab79c3fb0bb897d6a7f65c050deffe153e4b8f2d
Randao Reveal:
0xa59252c61b8e38e0726a580f8e3dc9627b9e1b6c08e3c3e855678a01d123b5b321b2ab86a5ec211c42b1902492a71d6d0f57b11b5d4f85822a2d82629d7639e4ddf4baf92cd880ec8a2e2193fc3bc47ed0730aeb4828ea5b9f18768ee73edd20
Proposer Fee Recipient:
0x87b3f3C934A13C779e100a5d6E6d7ef577e86671 (Fee Recipient: 0x87b3...671)
MEV Reward:
0.019175165507303357 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (44.44%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (44.44%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000524288 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.