Transaction

0115a50f2a19dcea3f7af95c4b4e45d2eaa21fddf71d97a8f2c51badb24d2da5
Timestamp (utc)
2024-03-24 18:23:37
Fee Paid
0.00000013 BSV
(
0.00910333 BSV
-
0.00910320 BSV
)
Fee Rate
10.01 sat/KB
Version
1
Confirmations
98,111
Size Stats
1,298 B

2 Outputs

Total Output:
0.00910320 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=2151.msg28228#msg28228">Quote from: satoshi on December 08, 2010, 08:21:49 PM</a></div><div class="quote">Any time you take an action based on payment amounts received, you always need to go back to bitcoin and ask for a current balance total (or use move or sendfrom), and be ready for the possibility that it can go down.<br/></div><br/>So it would be a design problem in the developper's app, not a problem inherent to listtransactions. What you're saying is: if listtransactions is used without care, it can be dangerous. OK, but many programmatic tools have traps too. For example, programming with threads is full of design traps. That doesn't mean that that tool shouldn't be made available to developpers, but that the documentation must warn strongly about those traps.<br/><br/>My point: let's make listtransactions available, but document it precisely, like any API, and explain the design mistakes that shouldn't be made when using it.</div> text/html
    https://whatsonchain.com/tx/0115a50f2a19dcea3f7af95c4b4e45d2eaa21fddf71d97a8f2c51badb24d2da5