Block
#22456901
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
297 days ago (May-11-2025 01:41:59 AM +UTC)
Transactions:
135 transactions and 67 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
BuilderNet in 12 secs
Block Reward:
0.118680244680794994 ETH (0 + 0.153742808502405156 - 0.035062563821610162)
Total Difficulty:
0
Size:
60,179 bytes
Gas Used:
12,669,582 (35.19%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000002767460191 ETH (2.767460191 Gwei)
Burnt Fees:
🔥 0.035062563821610162 ETH
Extra Data:
BuilderNet (Flashbots) (Hex:0x4275696c6465724e65742028466c617368626f747329)
Ether Price:
$2,514.75 / ETH
Hash:
0xffa685ce33fe619c03da7337f234fa702d05489f7cc13f07cb4ed4e9518982ae
StateRoot:
0x9f673a5af5d256b048c2accb27bcd4c70003d886652c383e1e4263b4a9a816ed
WithdrawalsRoot:
0x8e1222a7db676fe42adba21b733b461b1353b3282762fc0dcbb9aee14a63b89a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xade2a52551530c9d77f49572621a129e29a7b9db37759b6749cfc280dc5ea381
Parent Root Hash:
0x4e3796621d2bf275e64df5e833498518f8e12dd63089b1994f127ce2571d429f
Beacon Chain Deposit Count:
2049489
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x796f6d785b8ceeb7409406af6d59bf2012c56ccf22a956f452ee9beb81fca6b1
Randao Reveal:
0xb71d619e1df13762b4ceb5ea2b65ba548c42d13e972e36491f28690508bdcfb2c517029b8e42dc483c773f49aceb899217a226bbfc193142f3364489c34215f405514707c87baacff45d7e95e839d437c6bfcfe7c7b7fe01e9df9b4f0977cdb9
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.240800143848230582 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.