Block
#22086089
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
341 days ago (Mar-20-2025 05:49:23 AM +UTC)
Transactions:
207 transactions and 47 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.012311320980400886 ETH (0 + 0.019109637018645734 - 0.006798316038244848)
Total Difficulty:
0
Size:
75,461 bytes
Gas Used:
15,475,668 (42.99%)
Gas Limit:
35,999,965
Base Fee Per Gas:
0.000000000439290636 ETH (0.439290636 Gwei)
Burnt Fees:
š„ 0.006798316038244848 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,982.66 / ETH
Hash:
0xe42292dbd26cfb17866d3c0c762ae3aab9be0e133abb81fb8d34ae0b2b422cb4
StateRoot:
0x84b85f15214a79c8c1580f35e02161802d65b402135c8fafcbe827f790f460a6
WithdrawalsRoot:
0xc604b27f56507d1dd6bf78230327c0585ff38313cf9a4b4cec83f1103d59277e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x82d61f8dba5f6041a9101a766c477779599642f70a50e6f77211db38e20fea89
Parent Root Hash:
0xb3f9ec9c7afe29ff0a6901b802ad5bab9b9b04ac21a220a493476d8c50e880d8
Beacon Chain Deposit Count:
1967530
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x69270edaa11778fd3504bbcc3feee6bc38c5b1f12852cf80e835ea3575a7a441
Randao Reveal:
0x8ddc2f68b43ef74a6b570c8e94a7ef203612c4a8f975ef250239ef5049eda87d49d82b4395cb66ab6f9a4f73933fe6da10b54f687adc48ef6bcd995a7636ca07be4faa5bcdb4f47ab5af2ba5b6d0f826f40ac7b27b3b5d452eb7c6460646dc28
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.013086319744018408 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:
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.