Transaction

5fed8978c8a0c6fe40daa24fcbe2fa468afeffe016dbe2003a944d41a39ccdf4
Timestamp (utc)
2024-03-24 18:23:37
Fee Paid
0.00000017 BSV
(
0.00925693 BSV
-
0.00925676 BSV
)
Fee Rate
10.44 sat/KB
Version
1
Confirmations
98,335
Size Stats
1,627 B

2 Outputs

Total Output:
0.00925676 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM^<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=2151.msg28330#msg28330">Quote from: jgarzik on December 09, 2010, 12:58:05 AM</a></div><div class="quote">I agree with you and satoshi about "txs after &lt;txid&gt;". &nbsp;My listtransactions (now xlisttransactions) patch pointedly does not have that feature, and never has.<br/></div>As long as the interface is designed for things like showing the user the last N transactions history, it's fine, now that we have the Accounts feature making it easier to do payment detection the right way.<br/><br/>Gavin, could listtransactions have an option to list transactions for all accounts?<br/><br/>I'm not sure what the interface could be, maybe:<br/>listtransactions &lt;JSON null type&gt; [count]<br/><br/>It would be hard to do that from the command line though. <br/><br/>I can't think of a good solution for the interface, that's the problem.&nbsp; Maybe "*" special case like "" is. &nbsp;Everyone would have to make sure no user can create account name "*".<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=2151.msg28572#msg28572">Quote from: jgarzik on December 09, 2010, 04:13:50 PM</a></div><div class="quote">Sure, and that's easy enough to track with transactions.<br/></div>I don't get how that's "easy" to track with transactions.</div> text/html
    https://whatsonchain.com/tx/5fed8978c8a0c6fe40daa24fcbe2fa468afeffe016dbe2003a944d41a39ccdf4