Block
#22050227
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
347 days ago (Mar-15-2025 05:36:11 AM +UTC)
Transactions:
129 transactions and 47 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.023147853068779599 ETH (0 + 0.027386266996581543 - 0.004238413927801944)
Total Difficulty:
0
Size:
42,119 bytes
Gas Used:
8,427,386 (23.41%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000000502933404 ETH (0.502933404 Gwei)
Burnt Fees:
š„ 0.004238413927801944 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,937.46 / ETH
Hash:
0xa385b5eb78a20c473ec53d446f58bfca45a73dfd48e72e936ee17c35f6a66cb6
StateRoot:
0x994398d9400d947a148a1d42f254bbc472fc7f8ad9cc33afab412d1934892339
WithdrawalsRoot:
0xf71f8825eae7b467a3b4bdd15e054e715ebc22fa56dfc26d4da939d1d7fa6866
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x3f57877006350e0e03f421d8511cda9f5436d3b93cde96220a26fb7c066ee147
Parent Root Hash:
0xe96fa3983fa2111b87a7c7cce0abf3aab56a0093ec1c2c8467afac765511d33c
Beacon Chain Deposit Count:
1956645
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xe54429d043e699deb1fee3e4fc92176150ff73e044ceae40c6aef59e82c024bc
Randao Reveal:
0x8a9410c2a3d4e6bf190f9ca0200fe799f5cdccdafc0611ef674feb40f97e336671e15896304720a99a74e5b57ccf901e0a460cf540800ac685c281205482f04c744467d66f47fd172a0a3b4dc3240810f10161f06528e3a11dc49b09cdd1f455
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.027779036618251763 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
0.000000000000495429 ETH (0.000495429 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000064936869888 ETH
Excess Blob Gas:
43,778,048 (334 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.