Block
#17164405
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1030 days ago (May-01-2023 07:10:11 AM +UTC)
Transactions:
172 transactions and 70 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.075349804492701665 ETH (0 + 0.630037209330732171 - 0.554687404838030506)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
72,347 bytes
Gas Used:
14,176,142 (47.25%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000039128234243 ETH (39.128234243 Gwei)
Burnt Fees:
š„ 0.554687404838030506 ETH
Extra Data:
by @builder0x69 (Hex:0x627920406275696c64657230783639)
Ether Price:
$1,831.54 / ETH
Hash:
0x8e7f5fd9275176e1e9936c79e601042fea650e7228af67d21832a01224be7d0f
StateRoot:
0x191a94830745516961f9008f6743c1c5446a5617e8043c7b8ceba2fce353a821
WithdrawalsRoot:
0x5ac3f91ed41392cd43eec805a5996a7f31b1e5de64418664d301a22616c873cb
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1479d8b94339766838b8b6bccd02d5bcd3d1e8580758b10bfd8d984a1e48ed99
Parent Root Hash:
0x9da9736b9f57164530bde8c52a42ddca8490d0ddd6c7469a257da30329fae417
Beacon Chain Deposit Count:
634594
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x6f3fb544e1d4736045a1320cba4294703f37ae9ef40a8d5d91386438387a1580
Randao Reveal:
0xad04cfde9704ce3a5d8ebca081ef436700db28ab6912f9cce03f0e3e84866d32caa1924213e8f262477bbd1afabf56e7076e77c76df072233609725989e94fd4cef63cf4ea44496555907c22c528bb65f423e7b3bbc60270aa567dd2da5aff72
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.079988760105354692 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.