Transaction

ac8a4f673935451999514b2c27a78b4f91d7f7ddacfe65eb8bd40c0db3fb787d
Timestamp (utc)
2024-03-22 09:36:30
Fee Paid
0.00000015 BSV
(
0.00904131 BSV
-
0.00904116 BSV
)
Fee Rate
10.7 sat/KB
Version
1
Confirmations
92,299
Size Stats
1,401 B

2 Outputs

Total Output:
0.00904116 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM}<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1530.msg17955#msg17955">Quote from: theymos on October 21, 2010, 10:00:26 PM</a></div><div class="quote">his block count remains "stuck" at 1698.<br/></div>He was generating invalid blocks at difficulty 1.0. &nbsp;He must have a corrupted entry in his blk0001.dat or blkindex.dat file. &nbsp;He just needs to delete blk*.dat and let it redownload.<br/><br/>The safety lockdown detected the problem and was displaying "WARNING: Displayed transactions may not be correct!" because it saw a longer chain existed that it was unable to accept. &nbsp;The safety lockdown cannot stop generation or it would create an attack possibility.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1530.msg18074#msg18074">Quote from: gavinandresen on October 22, 2010, 02:25:14 PM</a></div><div class="quote">The Bitcoin client really shouldn't allow coin generation until you have all of the blocks up to the last block checkpoint.<br/></div>Good idea, I made a change to make sure it won't generate before checkpoint block 74000.<br/></div> text/html
    https://whatsonchain.com/tx/ac8a4f673935451999514b2c27a78b4f91d7f7ddacfe65eb8bd40c0db3fb787d