Transaction

7d1414d8210e4e58381d8aad564660cc0c8c0809dfd2ab017c2c39f9d6cfc976
Timestamp (utc)
2024-03-23 00:42:24
Fee Paid
0.00000013 BSV
(
0.03778458 BSV
-
0.03778445 BSV
)
Fee Rate
10.11 sat/KB
Version
1
Confirmations
95,961
Size Stats
1,285 B

2 Outputs

Total Output:
0.03778445 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Here's an answer to a similar question about how to recover from a major meltdown.<br/><a href="https://www.bitcoin.org/smf/index.php?topic=191.msg1585#msg1585">https://www.bitcoin.org/smf/index.php?topic=191.msg1585#msg1585</a><br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=191.msg1585#msg1585">Quote from: satoshi on June 14, 2010, 08:39:50 PM</a></div><div class="quote">If SHA-256 became completely broken, I think we could come to some agreement about what the honest block chain was before the trouble started, lock that in and continue from there with a new hash function.<br/><br/>If the hash breakdown came gradually, we could transition to a new hash in an orderly way.&nbsp; The software would be programmed to start using a new hash after a certain block number.&nbsp; Everyone would have to upgrade by that time.&nbsp; The software could save the new hash of all the old blocks to make sure a different block with the same old hash can't be used. <br/></div></div> text/html
    https://whatsonchain.com/tx/7d1414d8210e4e58381d8aad564660cc0c8c0809dfd2ab017c2c39f9d6cfc976