Block
#17529123
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
978 days ago (Jun-21-2023 04:07:59 PM +UTC)
Transactions:
253 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.063748040346196502 ETH (0 + 1.162761404970771852 - 1.09901336462457535)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
162,534 bytes
Gas Used:
16,778,350 (55.93%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000065501873821 ETH (65.501873821 Gwei)
Burnt Fees:
š„ 1.09901336462457535 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,889.69 / ETH
Hash:
0x6fef8f9bfababa05dd3e36f428c7acb7b98879bb1475b58600c01693d9cbd30f
StateRoot:
0xbc1cbeb5025d3b51140145b9fa1e36c907b0ac15a53c7ed27a56c64b2e788bf7
WithdrawalsRoot:
0x0858cab81331198c0820d6ad40461f0519f7c9f14b17d8071200a3c23f3953b9
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x893f59a7d5ef94134a5b67f27ad3ce92c711c2dafd59aba1f28159ddf7082040
Parent Root Hash:
0x5b4683fba65b1aaa54a404e1ad88f12062d106b319e983e13c68b7d8c1c37c56
Beacon Chain Deposit Count:
813331
Slot Graffiti:
poapqFgrWg9hW8Idd4BhhVcEK+YLMu0A (Hex:0x706f617071466772576739685738496464344268685663454b2b594c4d753041)
Block Randomness:
0xec3aa295877564b319854722348d02f41678346e2fb04078070cf3d72e2ed1c7
Randao Reveal:
0x9161da8d92d9955f8bef12ddadfd7031c752e5b5f40c9d08c86b155c4ea841908d60e78edf9b6544b366a6c17c04af4e14309cefa91773a5d1bca630765f99b37cb3b399f8b78d2a55265250c2d3c6ef4e90f01dc6bdc7a72636844f3668b940
Proposer Fee Recipient:
0x9f4B4CeCa7aCE96834Bd2fcC961c772De7cb481a (Fee Recipient: 0x9f...81a)
MEV Reward:
0.060192537033465428 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.