Transaction

8e4357ffd01bbdd92205bc0f1e6e5de7ea6d8c1f76d2c0ff0a9b0725fb3d503e
Timestamp (utc)
2024-03-25 01:19:36
Fee Paid
0.00000026 BSV
(
0.00481872 BSV
-
0.00481846 BSV
)
Fee Rate
10.29 sat/KB
Version
1
Confirmations
96,849
Size Stats
2,526 B

2 Outputs

Total Output:
0.00481846 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMá<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=723.msg7861#msg7861">Quote from: mkrogh on August 06, 2010, 03:12:18 PM</a></div><div class="quote"> <br/>Yes, that is my requirement, and will be most others as well. You will see almost no companies that sell without a guarantee against double spending.<br/><br/></div><br/>Did you know about this? You don't need to wait for it to get in a block to have way better certainty than PP or checks.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=423.msg3819#msg3819">Quote from: satoshi on July 17, 2010, 10:29:13 PM</a></div><div class="quote">I believe it'll be possible for a payment processing company to provide as a service the rapid distribution of transactions with good-enough checking in something like 10 seconds or less.<br/><br/>The network nodes only accept the first version of a transaction they receive to incorporate into the block they're trying to generate.&nbsp; When you broadcast a transaction, if someone else broadcasts a double-spend at the same time, it's a race to propagate to the most nodes first.&nbsp; If one has a slight head start, it'll geometrically spread through the network faster and get most of the nodes.<br/><br/>A rough back-of-the-envelope example:<br/>1&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br/>4&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1<br/>16&nbsp; &nbsp; &nbsp; &nbsp; 4<br/>64&nbsp; &nbsp; &nbsp; &nbsp; 16<br/>80%&nbsp; &nbsp; &nbsp; 20%<br/><br/>So if a double-spend has to wait even a second, it has a huge disadvantage.<br/><br/>The payment processor has connections with many nodes.&nbsp; When it gets a transaction, it blasts it out, and at the same time monitors the network for double-spends.&nbsp; If it receives a double-spend on any of its many listening nodes, then it alerts that the transaction is bad.&nbsp; A double-spent transaction wouldn't get very far without one of the listeners hearing it.&nbsp; The double-spender would have to wait until the listening phase is over, but by then, the payment processor's broadcast has reached most nodes, or is so far ahead in propagating that the double-spender has no hope of grabbing a significant percentage of the remaining nodes.</div></div> text/html
    https://whatsonchain.com/tx/8e4357ffd01bbdd92205bc0f1e6e5de7ea6d8c1f76d2c0ff0a9b0725fb3d503e