Block
#21870012
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
370 days ago (Feb-18-2025 01:35:35 AM +UTC)
Transactions:
149 transactions and 54 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.007674085528352807 ETH (0 + 0.017203982132981567 - 0.00952989660462876)
Total Difficulty:
0
Size:
61,351 bytes
Gas Used:
13,524,195 (37.60%)
Gas Limit:
35,964,845
Base Fee Per Gas:
0.000000000704655368 ETH (0.704655368 Gwei)
Burnt Fees:
š„ 0.00952989660462876 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,670.43 / ETH
Hash:
0x661c37013821ce2cdc5695cfe9595b05f6aac7e5c497a51de50feca67c7d152f
StateRoot:
0x1e504f4d056a4290d7c9a1b4c7167ce324a25e785b20c185cfe33839c4699972
WithdrawalsRoot:
0x7287371dc609ac03211782fc236b95a8f6706b3c2820af3135f34384445cc959
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xdf3876417da5b14e667a83200d0adfe6b1bf2e8f052acac39bd9757e2038d0f8
Parent Root Hash:
0x77c5d85d0a9116a2df6934c526b32d9f11f89b2e9792984feac3b7343e2bdea6
Beacon Chain Deposit Count:
1917023
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xf71f216d37fc487fbfd96c79994f2fc2ac4453157a29503e1b3cde349dd6c70b
Randao Reveal:
0x893d5cbf90ebe19bd29f3aebd00c9e8eb85f796741df0ef62bfd092527397f2092b283af68fc23b45e41567531041588025744c279766a0d21aa080fd317fe9ca6a814fbb8339d36ce80ecdbdc6e4d664384f1d79aa22d1aeb09df7dfe53e0b9
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.048697211324489886 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
0.000000000010591249 ETH (0.010591249 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000694108094464 ETH
Excess Blob Gas:
54,001,664 (412 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.