Transaction

8d4cb33e2b4e79c4351dcb1f981c0a000524a0f2ceb2cd60d13d56b150e31e87
Timestamp (utc)
2024-03-22 20:52:26
Fee Paid
0.00000013 BSV
(
0.00133998 BSV
-
0.00133985 BSV
)
Fee Rate
10.62 sat/KB
Version
1
Confirmations
97,336
Size Stats
1,223 B

2 Outputs

Total Output:
0.00133985 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÊ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=782.msg8768#msg8768">Quote from: Ground Loop on August 11, 2010, 05:31:24 PM</a></div><div class="quote">News to me is that *all* your coins are at risk.&nbsp; I thought it was just clumps of coins (previously received transactions) involved in the transaction, not my aggregate balance.&nbsp; Yikes.<br/></div>You were right before. The reason all of his coins were lost is that he first transfered all ฿9000 to himself, merging them into a single TxIn. If he had skipped that step and gone straight to sending himself ฿1, he would have only lost the smallest payment that he had previously received that was over ฿1.<br/><br/>I think the client needs to communicate TxIns and TxOuts better to the user. I don't know how to do that without being confusing, but there are real privacy, safety, and security implications in which coins the client chooses to transfer.</div> text/html
    https://whatsonchain.com/tx/8d4cb33e2b4e79c4351dcb1f981c0a000524a0f2ceb2cd60d13d56b150e31e87