Block
#17563923
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
981 days ago (Jun-26-2023 01:34:11 PM +UTC)
Transactions:
186 transactions and 60 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.072221732045303311 ETH (0 + 0.282149969033345311 - 0.209928236988042)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
168,706 bytes
Gas Used:
16,975,170 (56.58%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.0000000123667826 ETH (12.3667826 Gwei)
Burnt Fees:
🔥 0.209928236988042 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,859.19 / ETH
Hash:
0x8fc28b8594e171e1bf01091433e0f92364870201a4dbff5abd8d0af53a389cdd
StateRoot:
0xe9f10558929e62c6c5e2b37eda79b4e7a6a911afb5966f248dd63ae8fe1df262
WithdrawalsRoot:
0xbe572c6625b39691abd7686544862d6a72266354dd081a1da638ddb2f7a21a0e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x512bb7441d709449a3f341bfa0bd927749439ed3c998aa67f03a6589524e95f1
Parent Root Hash:
0x72bae9a70087a8e0d46ee77cb9bd12e3a7ffa4543e9cf190c45ffc8c7e4fc250
Beacon Chain Deposit Count:
824962
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3b5bae4fe92b31fb3d3e31531ad735be2a301b7c1fd76ffca27615f63ee2255b
Randao Reveal:
0x8e9133c792271a51d97f9c1fc0cf8f7e1789441be1de843c1fafa57c9bd3f6dc3394de82ec8d569e56b9a2e7fe02e5ef137e6ce7dab0671acf152217c1443e2653036522e970f197c8cc70a666793654e15beb2e2ca1113735374d598d8b50c9
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.102076054758586792 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.