Block
#22122933
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
334 days ago (Mar-25-2025 09:09:35 AM +UTC)
Transactions:
183 transactions and 44 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.011985302903135365 ETH (0 + 0.017819300478898288 - 0.005833997575762923)
Total Difficulty:
0
Size:
69,564 bytes
Gas Used:
13,985,559 (38.89%)
Gas Limit:
35,964,845
Base Fee Per Gas:
0.000000000417144397 ETH (0.417144397 Gwei)
Burnt Fees:
š„ 0.005833997575762923 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,066.62 / ETH
Hash:
0x3f14de37b7049fea7b73f9863c35d2036f94788d85b5eb43d37843829a9686a0
StateRoot:
0xce98a9ee1b9ad807a2599be4b213623c1d822066ea1f463f90fb318252176ddf
WithdrawalsRoot:
0x392019c84061acbd0855a227ec73bcf64ba1c71ee6ce3ffc2f4625a004269fec
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8b16a1ac438232bee53abeaa6a693bd67b57e4a520599b72b21d5c4d9d344623
Parent Root Hash:
0x4c8de019845b04f54cbec28b43db0c01fcbbe23fb68939218d95bc644509d06d
Beacon Chain Deposit Count:
1982176
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x7f8ddffc4372ab5bb068b73c5b8a6f41eee36dd72fdb88282ad2d2a00c54e1f6
Randao Reveal:
0xacca4c796ed5a81bb50752197aa298b44629c921b25bd438355bc3bd9800133df7c25281fc07428b16df38aebad3bb1e0f39532088467f4bc943d33d82441c6737e01b55eaa97e27744eb9ef8602b83e5c86ea928ba5577bf5539eada92194f7
Proposer Fee Recipient:
0x3C3EDD7EcD0B58472CDBe3c742827799b3CF92b6 (Fee Recipient: 0x3c3e...2b6)
MEV Reward:
0.008930421381346326 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000000065536 ETH
Excess Blob Gas:
1,048,576 (8 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.