Block
#17961318
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
916 days ago (Aug-21-2023 06:28:47 AM +UTC)
Transactions:
140 transactions and 63 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.021492900026745943 ETH (0 + 0.176199904301828518 - 0.154707004275082575)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
186,405 bytes
Gas Used:
13,253,725 (44.22%)
Gas Limit:
29,970,705
Base Fee Per Gas:
0.000000011672718747 ETH (11.672718747 Gwei)
Burnt Fees:
š„ 0.154707004275082575 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,667.27 / ETH
Hash:
0x3bd74f225b7cf3fa7f7f54764c55c040bc6f77fffb36ad9049c6ba2c9512fd54
StateRoot:
0x7febc654eb7d0ea4b8f3297fbdfd9eb025fe018c3a90abc1f5dcc9d509aaae26
WithdrawalsRoot:
0x423eae022d0737b1aa3b397f21e1f6782ceb354eaca3dd99b1118b2bc72385f5
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x30306605417a527f2112266c39c15b014009f45c8ab113dce34b19ee40579c29
Parent Root Hash:
0x3be1e7a9bae4e4269db497c355026a825f3561d6e344291606a9b345a201e6e4
Beacon Chain Deposit Count:
919771
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x4920abce8bcde03193c44ec59a4c6b8f073db4f69156e46ea37b054034c77555
Randao Reveal:
0x846e845eb09489373df40ae5a6f5c2f2196499bfe9ea0ca01c5f7d80bf664fe531e304ce9477b2fe4cfda6834aa5c60511f196862e8998444b4185b892a8dcca165231e117eb734312d2a363d4e2c11c4589a9df58d4a914d3679e6d1242bb43
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.024114960011916813 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.