Block
#17382019
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1007 days ago (May-31-2023 11:10:11 PM +UTC)
Transactions:
199 transactions and 103 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.143315045683442164 ETH (0 + 0.673801653889212022 - 0.530486608205769858)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
202,352 bytes
Gas Used:
21,797,262 (72.66%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000024337304759 ETH (24.337304759 Gwei)
Burnt Fees:
🔥 0.530486608205769858 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,874.04 / ETH
Hash:
0x78c68efd440ea290823c3b97ac8a988b7da7810cca7cd21a342a210831cdb0ad
StateRoot:
0xc7a2fcfcad46de1f08d9ae9bde1aa00353e960f00fe5637f3fce2a267e71d3d8
WithdrawalsRoot:
0xb7936546d4dd0104869f06a591e8b87bd8cba931d5de39d8f89e1ca19beb3d40
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x12c7556ed59d397e987d3d3e11508df07a602733863fe85977cdd9034f5769a2
Parent Root Hash:
0x362d6efb84b13c32e4e33ec8cd2da1893af377b570e46b4d9985443577b54118
Beacon Chain Deposit Count:
755907
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xfd7e625ee366f0baaa10854bd8b0768ee6872d5248ac25c4b53bfe07a4a854b5
Randao Reveal:
0x85414f51616fc9213aa7c0cba987d83389ef73aff573a848af65bc39d18f6a28ded9b6f758f5252b21596ad91f5fe1e512924c104a37f46ee8712730c462a0bc5752229847e17eb73a23ef05696085dbc0ca57516f5f1f35e632f86b758ced6a
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.139542833824113676 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.