Transaction

e5a65df302f9ce7dbbf0ffcf148ad9a9ea8f2197c9d84be53598eefa5a1fe2d6
Timestamp (utc)
2024-03-22 17:37:57
Fee Paid
0.00000016 BSV
(
0.00372049 BSV
-
0.00372033 BSV
)
Fee Rate
10.08 sat/KB
Version
1
Confirmations
93,794
Size Stats
1,586 B

2 Outputs

Total Output:
0.00372033 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM6<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1931.msg24518#msg24518">Quote from: jgarzik on November 26, 2010, 01:47:43 AM</a></div><div class="quote">Who said untrusted? &nbsp;The proposal is that you distribute blk0001.dat (and only blk0001.dat) in the bitcoin.org official client downloads. &nbsp;And of course the client will spend some time verifying blk0001.dat upon first use. &nbsp;This is unavoidable, and nobody has proposed changing or eliminating verification.<br/><br/>Just shipping blk0001.dat with official bitcoin would eliminate several headaches that new bitcoin users continue to experience.<br/><br/></div><br/>My personal suggestion is to have the block data as a separate download, but strongly recommended.&nbsp; If you want to simplify the installation for Windows users and otherwise clueless computer users that can't take a block file of this nature and put it into the correct directory, perhaps setting up a formal installation file to put it where it needs to go would be more "user friendly", but all it really has to contain is just the block data.<br/><br/>The purpose of this is mainly so those who are updating to a new version can do so without having to also keep downloading the same block data, which by definition is going to grow over time.</div> text/html
    https://whatsonchain.com/tx/e5a65df302f9ce7dbbf0ffcf148ad9a9ea8f2197c9d84be53598eefa5a1fe2d6