Transaction

d86d3c1fb37f14a07d7920a0fe7ddcf3eaba2c633eebb2a13a8a1b96bfec8d74
Timestamp (utc)
2024-03-23 16:39:32
Fee Paid
0.00000011 BSV
(
0.02671787 BSV
-
0.02671776 BSV
)
Fee Rate
10.12 sat/KB
Version
1
Confirmations
98,770
Size Stats
1,086 B

2 Outputs

Total Output:
0.02671776 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMB<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1269.msg13831#msg13831">Quote from: satoshi on September 23, 2010, 04:19:08 PM</a></div><div class="quote">In the next release (0.3.13), I'm going to change the format of the internal version number integer from 313 to 31300, for instance 31305 = 0.3.13.5.&nbsp; The last number represents changes on the SVN between releases and ought to be properly represented in the version number.&nbsp; Otherwise, it would be a pain if we had a mistake or something in one of the sub versions that needed to be worked around.<br/></div><br/>Thanks for the heads up. I'm actually checking version on my web apps, to assert if backupwallet is available, but as my private version is now widespread, it should be very simple to cope with that change.</div> text/html
    https://whatsonchain.com/tx/d86d3c1fb37f14a07d7920a0fe7ddcf3eaba2c633eebb2a13a8a1b96bfec8d74