Block
#17248841
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1021 days ago (May-13-2023 04:57:59 AM +UTC)
Transactions:
125 transactions and 55 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.16829180427921253 ETH (0 + 0.655795196635595042 - 0.487503392356382512)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
66,127 bytes
Gas Used:
11,792,152 (39.31%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000041341342306 ETH (41.341342306 Gwei)
Burnt Fees:
🔥 0.487503392356382512 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,796.24 / ETH
Hash:
0x78aae3cd51cc58a26900188d63bd78d8b5efe33d4be48ec971131a5195f9f674
StateRoot:
0x62b0f100a87db69739f22f87bb8ba71e8e2cb29d6c87aa0948b2f889ade12903
WithdrawalsRoot:
0x98b15a635ba02ee2b1fe152fdfc284013d46eab5f0f48b448847301d4caf309f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xef5b991b853311873a29df39c3355d3c784f8ac617cced3fe9711d09cce67f1c
Parent Root Hash:
0x9776c106b09d8a028233046c88d9f9825d5a137012734a395ced1be111149adf
Beacon Chain Deposit Count:
688655
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xcf1aa56a1c6d514639469046a4a0b4d711f2815fcc4320744943b0f915f0d440
Randao Reveal:
0xa40819e008beb1372b75d6d208bc4d8bf256b7af8da836f71827c3e6bfb1e3b4efa14fb2c9e4581bbecc8abeb6b78632100ff09b24e2d12d1064087d06224cc75693b7167d5d1c8e2a38732cb23aaebbc8a58b78a8e41bc1454ad4c9c5c1b1e1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.228729400383171005 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.