Sending bitcoin from Bitcoin-QT v0.6.2.2 wallet I bought a couple of bitcoin in 2012 where they languished on my successive Mac Book Pros in a Bitcoin-QT v0.6.2.2 wallet.  I now realise they are worth - ahem - something!  The wallet still fires up even though it is still calls itself a beta wallet and so I thought I would first try to send my lovely bitcoin to a new and glossy Exodus wallet.

Now being completely new to this I got my receive address for my Exodus Wallet and tried sending 0.1 BTC to my Exodus wallet. Eventually (maybe 5 hours later) it showed it had arrived but with zero confirmations. This first transaction still shows with 0.1 BTC "Pending" in the Exodus Wallet (sent Friday Dec 1st 10.04.10 PM).

I realised I had not included any fee on this first send but  I didn't see anything I could do about that.

Anyway I then sent the balance of BTC in my Bitcoin-QT wallet, but this time included a 0.0004 BTC fee to the same address.  But, 34 hours later it does not even show it having arrived at the Exodus wallet.

Now I really do not know what to do.  I assume if I leave my Bitcoin-QT wallet up and running it will keep broadcasting the transactions and so they may never disappear. So I have quit the wallet.  But suppose I leave it for a few days. If I fire up the wallet then I assume it will broadcast again and I will be back in the same situation?  I could start it up offline and restore from a backup I did just prior to sending the first transaction - I guess that would cut out the re-broadcasts.  Would that be the thing to do?

The Bitcoin wallet reports that the Transaction Ids are:

(Second transaction with 0.0004 BTC fee):

60efa66a8aef482cc3f2ce2ae348427e74feb12db91b579ed4c7ea955fbea0bf

(First transaction with fee not added :-(:

a0a70213c2e94119357cdac865e404e1ca6f44cf40a4acf9a6e272d4f0dd3f21

However when I put those into https://blockchain.info/ I am told the transaction does not exist. The same with ViaBTC Transaction accelerator.
I don't know exactly what features are available on your version, but here are some ideas to try.

First, take a backup of your wallet.dat file.


In the debug window (help menu?), make sure that your peer is actually connected to some other peers so that your transaction will be broadcast to the network.
Make sure your node is fully synced to the latest block.
Start the application with the -zapwallettxes=1 argument to delete the transactions that are not in the blockchain from your wallet.
Start again with the -rescan argument to scan the blockchain for bitcoins assigned to your private keys. This will take a long time (hours possibly).
Your bitcoins should be available again, so try to send the transaction again with a higher fee. You can use https://bitcoinfees.earn.com/ to decide what an appropriate fee is.


If you really want to export your private keys, you can use the dumpprivkey "address" command from the console inside the debug window (if the console is available in your version). But be very careful when moving your private keys around, they could get stolen by a key logger, screen grabber, other malware, or phishing sites, etc.