Block
#22061727
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
350 days ago (Mar-16-2025 08:07:47 PM +UTC)
Transactions:
177 transactions and 24 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.007258558097623425 ETH (0 + 0.013722630014261244 - 0.006464071916637819)
Total Difficulty:
0
Size:
59,553 bytes
Gas Used:
11,775,489 (32.71%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000000548942971 ETH (0.548942971 Gwei)
Burnt Fees:
🔥 0.006464071916637819 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,886.94 / ETH
Hash:
0x6efdccdaa9c8937b3cae997bf39a9c3d23642d8a1f328bcc2c2467044e9e902b
StateRoot:
0xe98257f258f643f7af2d4ba2dd072cb8f42ed91921010f6109cc2bde1dc9383a
WithdrawalsRoot:
0xd38c77284bb7e90ff8312afe04489deb29e565b109af65d0de6c7e289a487269
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x88542661d1fd84f1c9ddb30f2ec9e9e33d288441652917457ee9c0e60b1e780b
Parent Root Hash:
0xe33c56fda9ffe77082408fb018ae9360eb4ba5a65968379d38946a1f7e369ceb
Beacon Chain Deposit Count:
1957625
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x803cccb100c1dd9f95f4580e006080eb4cd16aa57049b033b64eb774dceb5500
Randao Reveal:
0xaa134f7f215308454e8e3ecfb010040aadc894d9386cb04cac43f67b9d7b9c1723cd3bf32dfa0f8e9030f23d0517c29619f684cdcba2a1aedc9c00c1582e8d70a2b35c4a291a737562b9bdffc3bb12b53f70fca81c7e8548208fdd8a662fe4f4
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.010043052445647181 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
0.000000000217701841 ETH (0.217701841 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000028534615703552 ETH
Excess Blob Gas:
64,094,208 (489 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.