Transaction

a28bc65c8d70ea20d5cf32ca3eb8ae991133b985bfae0e00e246c27b6080448d
Timestamp (utc)
2024-03-26 01:51:02
Fee Paid
0.00000016 BSV
(
0.01062098 BSV
-
0.01062082 BSV
)
Fee Rate
10.26 sat/KB
Version
1
Confirmations
96,701
Size Stats
1,559 B

2 Outputs

Total Output:
0.01062082 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=550.msg5349#msg5349">Quote from: satoshi on July 23, 2010, 06:24:56 PM</a></div><div class="quote">By making some adjustments to the database settings, I was able to make the initial block download about 5 times faster. &nbsp;It downloads in about 30 minutes.<br/><br/>The database default had it writing each block to disk synchronously, which is not necessary. &nbsp;I changed the settings to let it cache the changes in memory and write them out in a batch. &nbsp;Blocks are still written transactionally, so either the complete change occurs or none of it does, in either case the data is left in a valid state.<br/><br/>I only enabled this change during the initial block download. &nbsp;When you come within 2000 blocks of the latest block, these changes turn off and it slows down to the old way.<br/></div>The first part of the 70k downloaded in about 20 minutes, the rest of the remaining 2000 blocks in about 7 minutes, so only 27 minutes from 0 to 100%, very nice! Is there a safety reason to stop within the last 2000 blocks or can it be tweaked to stop at remaining 500 blocks for example?<br/><br/>In case anyone was curious, average download speed was around 3 Mbps for each burst of download.</div> text/html
    https://whatsonchain.com/tx/a28bc65c8d70ea20d5cf32ca3eb8ae991133b985bfae0e00e246c27b6080448d