Transaction

256afc1cc2cdca15f6c9ec4c1fc802cd4e5d2fbcf64fe535f2540393fbbb8cec
Timestamp (utc)
2024-03-24 12:26:54
Fee Paid
0.00000011 BSV
(
0.01311751 BSV
-
0.01311740 BSV
)
Fee Rate
10.31 sat/KB
Version
1
Confirmations
101,367
Size Stats
1,066 B

2 Outputs

Total Output:
0.01311740 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM.<div class="post">I like that in libraries for the external API's, but you can probably tell from the code that I'm not a fan of it for interior functions.&nbsp; Big obligatory comment headers for each function space out the code and make you hesitate about creating a small little function where the comment header would be bigger than the function.&nbsp; They're some trouble for maintenance, as changes to the function then require duplicate changes in the comment header.&nbsp; I like to keep code compact so you can see more code on the screen at once.<br/><br/>To add them now at this point, what would be written would just be what's obvious from looking at the function.<br/><br/>The external API we have, in rpc.cpp, the usage documentation is in the help string.<br/><br/>Sorry to be a wet blanket.</div> text/html
    https://whatsonchain.com/tx/256afc1cc2cdca15f6c9ec4c1fc802cd4e5d2fbcf64fe535f2540393fbbb8cec