Transaction

a4d13962903db4e46ca25bf5974c56a3894de0df26f32ebb1f6a01103e940f7f
Timestamp (utc)
2024-03-27 09:53:41
Fee Paid
0.00000012 BSV
(
0.00794722 BSV
-
0.00794710 BSV
)
Fee Rate
10.73 sat/KB
Version
1
Confirmations
91,787
Size Stats
1,118 B

2 Outputs

Total Output:
0.00794710 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMa<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=571.msg5728#msg5728">Quote from: Red on July 25, 2010, 07:22:14 PM</a></div><div class="quote">Satoshi pointed out that my scenario still required the hash function to be broken. That is true, but I was surprised to learn how successful some have been with that. MD4 and MD5 are obvious examples. But work is well underway at colliding SHA-1 and siblings like SHA-256.<br/></div>What they often don't mention though is *collision generating* still takes a lot of CPU time.<br/><br/>If I figure out that Public Key 123456 generates Hash ABCD<br/>and<br/>Public Key 654321 also generates Hash ABCD<br/>I'm still left without the Private Key.<br/><br/>But from what you are saying, all I need is Public Key 654321 and I can spend coin pretending to be Public Key 123456.</div> text/html
    https://whatsonchain.com/tx/a4d13962903db4e46ca25bf5974c56a3894de0df26f32ebb1f6a01103e940f7f