Transaction

b13d7c8e7a5b2630c6e3a4b95a0ce069da8df2c359a29a45daaa6bf9efcfcb6b
Timestamp (utc)
2024-03-22 08:53:29
Fee Paid
0.00000011 BSV
(
0.00959034 BSV
-
0.00959023 BSV
)
Fee Rate
10.39 sat/KB
Version
1
Confirmations
94,272
Size Stats
1,058 B

2 Outputs

Total Output:
0.00959023 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM&<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=360.msg3064#msg3064">Quote from: Bitcoiner on July 15, 2010, 02:31:52 AM</a></div><div class="quote">Could this be fixed in the next release? We were just discussing what would happen if a flaw were found: Here we go, our first real test of the situation.&nbsp; <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/></div>Nope! At least, not easily - block and transaction identities are based on this hash, among other things, so this would break the chain. You'd need to do a phased rollout - first, add parsing support to all clients, then obsolete older clients, then roll out a new version which generates a new version of the block serialization format using the new hashing method.</div> text/html
    https://whatsonchain.com/tx/b13d7c8e7a5b2630c6e3a4b95a0ce069da8df2c359a29a45daaa6bf9efcfcb6b