Block
#17176809
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1042 days ago (May-03-2023 01:01:35 AM +UTC)
Transactions:
159 transactions and 113 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.992655708579077926 ETH (0 + 2.237040869122169142 - 1.244385160543091216)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
84,311 bytes
Gas Used:
17,588,792 (58.63%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000070748756398 ETH (70.748756398 Gwei)
Burnt Fees:
🔥 1.244385160543091216 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,905.90 / ETH
Hash:
0x55f63d8e3f7fa6275430489f644a42faad9c6516c7e1b6ab74a929b6fc95b0c4
StateRoot:
0xcd445c83782b8641319f01e36d0132ced7598b035ac3b5a821b5ecd8a9c7b56a
WithdrawalsRoot:
0x3352bc812b026e8d40f83efb19f1fb29908f0380b63cb67b7d36ccbec0597601
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb88d05f96f39305c39285eaa02da723e9d559e22f6589d598816d441cd7a311e
Parent Root Hash:
0x1ef632a77cd53a7cf6b7664b9334b15b2c7a4af90d7cdcc2cd0cec6db0bbc4a3
Beacon Chain Deposit Count:
637981
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x75349fef5d6c49da6550cb5302cadf1f4533ccf46da779665fe9fe937de06841
Randao Reveal:
0xaaae854f682fc545dba3644313bcc8a589cade7e7d82a8e6f6fbc3915e3f7ff133382964f517031e7c515b30c6bea27f179cdc04c4ede0bac283b16508ee366d17bf951ff09578560f807b8ae867f6a505d912d873b37ccc0640d83b4c01dc5f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.984584129573138884 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.