Block
#17571924
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
974 days ago (Jun-27-2023 04:38:59 PM +UTC)
Transactions:
101 transactions and 26 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.04648729212962662 ETH (0 + 0.517064612215596244 - 0.470577320085969624)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
487,024 bytes
Gas Used:
14,945,656 (49.82%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000031485892629 ETH (31.485892629 Gwei)
Burnt Fees:
🔥 0.470577320085969624 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,889.74 / ETH
Hash:
0xf35ca9310056708107c8344ade04c50613a927c58cdfb7241f6530ec99e81f59
StateRoot:
0xc5bcc7d1c643d53b3c887557ae333bdae0cf05adfd93bcd7452ce83f7462b861
WithdrawalsRoot:
0x472407779be30b414d5a3eff6d85d462c8025d04271893b7690dc46f1c49dae8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2997fc084fdb8e1db68b1e0bf4527cc94992e5291769b205511965a83cb70446
Parent Root Hash:
0x1d69751950468f186218cf6c23cceb323cf07199a039988e0f3eb5487ed52546
Beacon Chain Deposit Count:
828223
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xe5771a8d91655229716905ab0f814b1d2f79d15acd08ff0ec418d5a1c36f6d71
Randao Reveal:
0xa7c377b98cff9997a2cd077ba8adc85e859b5d0549a1a12902f34cbb4401e2cfa7ff03daa6b166379eb3db9ff2f57deb0b60256a93653b9817cc3efc1e99fd104b63827df8c5c5ac8f8ee75bc27dd81b08aac5497d8b5171adf4c95e2e320565
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.049404331802086987 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.