Transaction

df0eba82b06d5689b38da8f0d8d4e08d83bacfe33036e8c2c922437fa96020f7
Timestamp (utc)
2024-03-22 14:03:50
Fee Paid
0.00000016 BSV
(
0.00600183 BSV
-
0.00600167 BSV
)
Fee Rate
10.06 sat/KB
Version
1
Confirmations
94,019
Size Stats
1,589 B

2 Outputs

Total Output:
0.00600167 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM8<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=287.msg7454#msg7454">Quote from: gavinandresen on August 04, 2010, 11:58:58 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=287.msg7443#msg7443">Quote from: bytemaster on August 04, 2010, 06:22:56 AM</a></div><div class="quote">Well, right now nothing stops someone from creating a system where:<br/><br/>A sends&nbsp; 1.00000001 to B<br/>B sends&nbsp; 1.00000000 back to A<br/><br/>Net result is a micro-payment and no processing fee.<br/></div><br/>... unless B started with zero bitcoins.&nbsp; Then B is stuck; she can't send 1.0 back, because doing that would cause a 0.00000001 bitcoin 'change' transaction, which would trigger the 0.01BTC fee, which they can't pay (because they only have 1.0000000001).<br/><br/></div><br/><br/>ok if a and b both start out with 1 BTC and agree to transfer 0.0001 using two inputs and two outputs on a single transaction can change a to 0.9999 and b to 1.0001. The rest of the network it would seem would accept the transaction.<br/><br/>The only stumbling block is whoever creates the transaction needs the private keys for both inputs which would come from different wallets normally. The one who creates the transaction could cheat.<br/></div> text/html
    https://whatsonchain.com/tx/df0eba82b06d5689b38da8f0d8d4e08d83bacfe33036e8c2c922437fa96020f7