Block
#17923366
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
930 days ago (Aug-15-2023 10:57:47 PM +UTC)
Transactions:
134 transactions and 69 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.023647758083508345 ETH (0 + 0.291445790799185055 - 0.26779803271567671)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
179,476 bytes
Gas Used:
15,062,385 (50.26%)
Gas Limit:
29,970,705
Base Fee Per Gas:
0.000000017779258246 ETH (17.779258246 Gwei)
Burnt Fees:
🔥 0.26779803271567671 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,827.22 / ETH
Hash:
0xbc112437742ac06a1345ef94ed9668a93e7b58ffaf7999e3412a007831525e20
StateRoot:
0xa8e17358b4b22358dbdbba8c40d5e7d89d685b7b57b0f44638567d21c6a3ac56
WithdrawalsRoot:
0x6d3544775118910293a09b06e54847320b4c2e3907e061f6c52088ace7e11b12
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xe491177e1e9e6d691569342b096da7335c3b091d5500ec87e44d8a5ac7e9c645
Parent Root Hash:
0x54a1b7d06a06b3da5cc89b1f9fdba466aee0473845d84220f8f0f92dcad7aca0
Beacon Chain Deposit Count:
910765
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x389c2032a7e4eb1d7d74c88d12b9bf45c37c6fbcafaf549a26b756edacec734c
Randao Reveal:
0xa627f0f3cddafe86a34b1974603c9784b9ec2de80e811bacc0e19366d10b991794a684369518fba4cabf72d3b1e9830607bc7b028ad20b08f5dd41907eb031203cc1171b5c2b70397928045ce23b9bfe083fd0939eff16c34daacb07a3d84d75
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.022452176871161022 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.