Transaction

481fdc2d86dae23b16899cdcb2eb2a0ce1b4c4a91cd6f6d2acbcfd250855dae8
Timestamp (utc)
2024-03-22 09:20:47
Fee Paid
0.00000014 BSV
(
0.00948623 BSV
-
0.00948609 BSV
)
Fee Rate
10.15 sat/KB
Version
1
Confirmations
94,170
Size Stats
1,379 B

2 Outputs

Total Output:
0.00948609 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMg<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1668.msg21896#msg21896">Quote from: satoshi on November 13, 2010, 11:25:26 PM</a></div><div class="quote">In support of the priority feature, SelectCoins only uses your own 0 conf transactions only as a last resort if that's all you have left. &nbsp;This helps keep you from turning your coins over rapidly unless you're forcing it by actually turning all your coins over rapidly.<br/></div><br/>Of course, if the network is not being flooded and you're not overly concerned about the current transaction getting held up then it's probably worth preferring to use your 0 conf transactions so that you can "save" the higher priority coins for when the network <b>is</b> being flooded.<br/><br/>Unless I misunderstand, it looks to me like the current logic is more likely to spend the accumulated priority of older transactions. It's a minor point however.<br/><br/>Gaming the system&nbsp; by including 1000 or so recently turned over BTC to bump the priority as described in my post above still works of course! <br/><br/>ByteCoin</div> text/html
    https://whatsonchain.com/tx/481fdc2d86dae23b16899cdcb2eb2a0ce1b4c4a91cd6f6d2acbcfd250855dae8