Block
#17856521
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
934 days ago (Aug-06-2023 02:29:59 PM +UTC)
Transactions:
159 transactions and 98 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.085669602581621689 ETH (0 + 0.472228324113406903 - 0.386558721531785214)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
225,829 bytes
Gas Used:
17,290,809 (57.64%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000022356312046 ETH (22.356312046 Gwei)
Burnt Fees:
š„ 0.386558721531785214 ETH
Extra Data:
by @builder0x69 (Hex:0x627920406275696c64657230783639)
Ether Price:
$1,827.82 / ETH
Hash:
0x46d0b338c58649af9306389146b45b6bab6e5813930c45f2a432b27291c5b0ec
StateRoot:
0x6a983d1dbaebacc7dc1bcca3b48a60d1be9e9afca47ee2b58d016e3720c6a98d
WithdrawalsRoot:
0x204fa7b1b1dea4e172df83931a4c7a282808772079eb8df09b053b5ad7073130
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x4c0f3c6a9bbc0877e9061fad9d4d6159c008729e4c4b8c9849472f3fdd6521c6
Parent Root Hash:
0xc21c8b35f3b6b0d3c595a5eb4aca342890ddf410984092f7a196834ea7aa8e28
Beacon Chain Deposit Count:
897053
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x364ee10d4c9e6e333b69c68b03243f420b083f01e148d468be09b42996527ec8
Randao Reveal:
0xa3098df8bfe93d581c5131d3cf5f5b6a5b08151d0a43663d51b694f1a96294c84478981ddfaa95eb322cdde5e25a4fc0187e9f4c33012c16bebbf62339af32be2ec62bc2ea3b80e2a1fe2fcf6eac3776bc0c15d5719fcc56371ef33c03844efc
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.086148704050652226 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.