Transaction

a107e5d830beff4e070d0c339a05f30364aa9f7e197ba17855ac5ffdce93f4a3
Timestamp (utc)
2024-03-22 15:35:09
Fee Paid
0.00000010 BSV
(
0.00499694 BSV
-
0.00499684 BSV
)
Fee Rate
10.36 sat/KB
Version
1
Confirmations
93,906
Size Stats
965 B

2 Outputs

Total Output:
0.00499684 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÈ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=832.msg9754#msg9754">Quote from: satoshi on August 16, 2010, 03:25:54 PM</a></div><div class="quote">It would probably be possible to initiate an AddToBlockIndex or Reorganize after the check, but it would require a lot more careful attention. &nbsp;I probably should break out part of AddToBlockIndex that sets the new best block. &nbsp;I'll probably end up doing that instead of the code below.<br/></div>This is what I ended up doing in SVN rev 139.<br/><br/>Instead of deleting the bad chain, I added an extra CheckBlock to ConnectBlock so bad blocks can't get back into the best chain once they're kicked out.</div> text/html
    https://whatsonchain.com/tx/a107e5d830beff4e070d0c339a05f30364aa9f7e197ba17855ac5ffdce93f4a3