Block
#21259289
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
456 days ago (Nov-24-2024 06:07:23 PM +UTC)
Transactions:
158 transactions and 50 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.028411939011315873 ETH (0 + 0.188763090190667483 - 0.16035115117935161)
Total Difficulty:
0
Size:
70,876 bytes
Gas Used:
15,071,926 (50.24%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010639061735 ETH (10.639061735 Gwei)
Burnt Fees:
š„ 0.16035115117935161 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,364.81 / ETH
Hash:
0x4985ca455d40040d98b406229793ecacd3b9b0e799b18c8e5b5b1b76fb874b3b
StateRoot:
0xe2958c9824b54a9d829feb37ff975598ffb175a2fa6d5de9950641d05ef2761d
WithdrawalsRoot:
0xde0ca5954d44a96e7d2b16bc29f66d6ab2a7248d97d825f46e11c07957fe81d4
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x71fbed98d99f6d9f418465b4cc183c929f480bcc3b5622421cf7c24df467f04b
Parent Root Hash:
0x5faea55d175566f744e12790f53ce97b3ca3253cf7e55ccfc2e604dc63444ea6
Beacon Chain Deposit Count:
1785059
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x2bce68c0b2c9da029897d050843219f0cf3eebfe294b5fea6d9f3a170cdaf343
Randao Reveal:
0x868d5ae07bc41904275034dd4cc204ff676d0357b1f918448d3533e5d3ed88727a1fd5549bdfe089b38feef9f885dfad0aebaf116e9dea2ea821f92c20fc84e2d8722e5c555261b1d73b35d47efa412812fe2e8339fe604c64d90f9be6d5c65f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.067837570240817944 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
0.000000019127498403 ETH (19.127498403 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.0100283178827121 ETH
Excess Blob Gas:
79,036,416 (603 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.