j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM#<div class="post">It appears that block 70718 was found two hours in the future and followed with block 70719 being found about two hours in the past (from the future date of previous block).<br/><br/><div class="codeheader">Code:</div><div class="code"> -7017 seconds to find block 70719<br/> 8153 seconds to find block 70718<br/> 49 seconds to find block 70717<br/> 524 seconds to find block 70716</div><br/><div class="codeheader">Code:</div><div class="code">block timestamp<br/>70715 1280275621<br/>70716 1280276145<br/>70717 1280276194<br/>70718 1280284347<br/>70719 1280277330</div><br/>This doesn't seem to have any effect on things so much other than providing a kind of inaccurate depiction of statistical results every now and then (when a block is claimed to be from the future or the past), however what would happen if either the first or second (whichever one triggers new difficulty being established) of a new set of 2016 blocks is generated to have a timestamp 2+ weeks in the past or the future? If in the past, I presume according to the code in main.cpp: GetNextWorkRequired function that the lowest accepted interval is 3.5 days. And if in the future I presume according to the code the lowest accepted interval is 56 days.<br/></div> text/html
https://whatsonchain.com/tx/6eda4e2062a4a8d47afaa5c2ac9f7b2aab61a3a61c233a34dc2a4f1b79d9e68c