Transaction

8ee1557a6000f99d2bc011dfeeca90fa45e731341e7fe6d44634f08be5db4ea2
Timestamp (utc)
2024-03-22 20:51:27
Fee Paid
0.00000017 BSV
(
0.00134665 BSV
-
0.00134648 BSV
)
Fee Rate
10.59 sat/KB
Version
1
Confirmations
94,350
Size Stats
1,605 B

2 Outputs

Total Output:
0.00134648 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMH<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=873.msg10297#msg10297">Quote from: satoshi on August 19, 2010, 08:14:01 PM</a></div><div class="quote">- Warning not to mess around with your wallet.dat file. &nbsp;It's a database file, it's not as simple as you think. &nbsp;In this Beta version, we haven't had time to try and tinker-proof it yet. &nbsp;It may not work as expected if you start swapping it around.<br/></div><br/>So how simple is it? I'm just now thinking about foolproof backups on the lottery site I posted about yesterday, and I'm struggling to find information on this. Can bitcoind dump it in a safe state, or at least flush it on request? If I backup the file mid transaction, do I loose the whole thing or just the update in progress? When do I need to backup? Every outgoing transfer is obvious, there are key pairs created automagically, but what about transfers received? the key pair we already had, no new address needed to be created afaict. Or does bitcoin do the same change dance on the receive side too?<br/><br/>This part is, I believe, the most critical of them all. While MSE and clock skews may prevent normal program usage, the wallet backup issues have made people loose a bunch of coins which, obviously, sucks and doesn't do much on supporting continued usage.</div> text/html
    https://whatsonchain.com/tx/8ee1557a6000f99d2bc011dfeeca90fa45e731341e7fe6d44634f08be5db4ea2