Transaction

3f3f47f02fb47e7f85f689789b6d2d8c4e96b75deee2fe0d3e688a6ffa192cdd
Timestamp (utc)
2024-03-22 01:47:53
Fee Paid
0.00000012 BSV
(
0.00186604 BSV
-
0.00186592 BSV
)
Fee Rate
10.68 sat/KB
Version
1
Confirmations
93,551
Size Stats
1,123 B

2 Outputs

Total Output:
0.00186592 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMg<div class="post">This is in SVN rev 147.<br/><br/>This is more standard, and although json-rpc 1.0 didn't specify the format of error objects, it did specify that they would be <i>objects</i> not strings or other values, so we needed to change this to be correct.&nbsp; The code/message members have become standard in later json-rpc specs.<br/><br/>If you have code that checks the error and expects a string, you'll need to change it.&nbsp; When there is an error, the error member is now an object not a string.<br/><br/>Also in SVN rev 147:<br/>- The command line json-rpc returns the error code as its exit code.&nbsp; Exit codes can only be 0-255 on unix, so it's abs(code)%256.<br/>- The "backupwallet &lt;destination&gt;" command that was discussed in another thread.&nbsp; It locks the wallet and copies it, so you can be sure you get a correct copy.<br/></div> text/html
    https://whatsonchain.com/tx/3f3f47f02fb47e7f85f689789b6d2d8c4e96b75deee2fe0d3e688a6ffa192cdd