Transaction

9cc0eb2e2ed6efbdb4e63fad3ef445a2125db237d39a0bf77062b4fb09179ddf
Timestamp (utc)
2024-03-24 13:10:01
Fee Paid
0.00000015 BSV
(
0.01270912 BSV
-
0.01270897 BSV
)
Fee Rate
10.22 sat/KB
Version
1
Confirmations
98,126
Size Stats
1,467 B

2 Outputs

Total Output:
0.01270897 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¿<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=287.msg7498#msg7498">Quote from: Insti on August 04, 2010, 02:58:31 PM</a></div><div class="quote"><br/>What exactly is this 'dust spam' that this 0.01BTC transaction fee "solving"?<br/>It seems to do more harm than good because it prevents micropayment implementations such as the one bytemaster is suggesting.<br/><br/>I'm not aware that the network is straining under the weight of the existing transaction volume.<br/>Anyone wishing to send a lot of transactions can already do this by sending x BTC to themselves a lot.<br/><br/><br/></div><br/>Someone with only one Bitcoin could send 100,000,000 transactions, which might overload the network. This isn't a good solution, though -- the vulnerability will still exist when the limit is lowered because someone will certainly be saving a bunch of Bitcoins.<br/><br/>A better solution would be to deprioritize transactions below 0.01 and completely drop them if there are more than 10,000 (or whatever) in the queue. Then these transactions would be slower and less reliable than other transactions, but they would work and not interfere with "real" transactions.</div> text/html
    https://whatsonchain.com/tx/9cc0eb2e2ed6efbdb4e63fad3ef445a2125db237d39a0bf77062b4fb09179ddf