Block
#17190528
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
965 days ago (May-04-2023 11:19:11 PM +UTC)
Transactions:
151 transactions and 126 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.288604791174888999 ETH (0 + 1.664018612759992423 - 1.375413821585103424)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
67,229 bytes
Gas Used:
15,023,804 (50.08%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000091548972656 ETH (91.548972656 Gwei)
Burnt Fees:
🔥 1.375413821585103424 ETH
Extra Data:
by builder0x69 (Hex:0x6279206275696c64657230783639)
Ether Price:
$1,878.56 / ETH
Hash:
0x9acc5108f854ccc694a8b5e34656bd61b47a88c2e5f9e492ab7055153db604ff
StateRoot:
0x168361e9a10206da2ee0735ea9c37d92372165d288d11445edede8b555053b65
WithdrawalsRoot:
0x41ed705aec57cb3e518e3ce0834c58448af402f6808bc030af6554ba543f097e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2197ce3afcbec4e16ab38d226bfc64fdfe4c1e76872786f0981542f129cf9d63
Parent Root Hash:
0xa77abb735a0cb18bd5fec1d3f4bf1a2d69d6c653f2f610008d8dffe8f2d33726
Beacon Chain Deposit Count:
647237
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0xc6316a0a7b1a462b9c449365f0dbbef7aa328b4d8af25c7dfe73fdba389793cc
Randao Reveal:
0xa27c23a5f3428ee61976a7412e997078547ee618a2b7113367baaa7db370e8fb150ef3d574a2160b28806a53584c81d318210a7d136e4465ca530f259da40e8ad5d2a4b019686550fb3bd9166e0374bef02e11a8e525633d99abd0287c36909a
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.289357909788425151 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.