Block
#17524821
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
981 days ago (Jun-21-2023 01:39:23 AM +UTC)
Transactions:
152 transactions and 94 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.026848422272366312 ETH (0 + 0.285045219045552425 - 0.258196796773186113)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
162,645 bytes
Gas Used:
20,372,661 (67.91%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012673690333 ETH (12.673690333 Gwei)
Burnt Fees:
š„ 0.258196796773186113 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,889.69 / ETH
Hash:
0x0473185e0a2b7d723e82ebe89d5f3262a1f5441b1c703cfdf17069f18070fb94
StateRoot:
0x543fc36f25438c752eeb425e8000427fe6b7be2fca1ab54c6626652fc5162d4d
WithdrawalsRoot:
0x4c0ebd740f3561823ff4117419837d260e7dba061b254f5c4c92635ff5eae728
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7c995b21952455b0316320f03fa77ff080f0beb4d7b638a062102567e907bd52
Parent Root Hash:
0xb452356951e655b3cb669583a15ba8abc77698f75b0c025196a20f93b143aaa7
Beacon Chain Deposit Count:
812090
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xa0fff0fd999f8bc6ffacedb0660f3f68ff7ecf8bf1b432475cfad4341dce1040
Randao Reveal:
0x8f27d6199b6e2735e568894d83aff9aa105ee54425908cf7dc84685dc88818dda58d1f3c8cd02fe8b4a337b45b1d4a7d0254e9e3536f4d4106eb2dba9a9a81dcb007f05f0d758832ae7844da66b2f041f15e2c32a06a26a43d13d99cdb5245bb
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.026990257936003379 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.