OK... This does indeed look like a big web of unconfirmed transactions, spending unconfirmed outputs from unconfirmed transactions, which (just to make this all "doubly" confusing) are double spends!
![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif)
As near as I can figure... The sequence of events goes something like this:
On 21st November 2017, you attempt to send 1 BTC to your Exodus wallet (1AEdg):
https://bitaps.com/ecb2527ab18ef6e27d7c6c0e818f3e043ebe3160d744e79164bf81014580b722For whatever reason, this transaction is NOT confirmed, despite the 1327 sats/byte fee!!?!
![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif)
Then, on 22nd November 2017, it seems you executed a double spend... basically the same transaction (1 BTC to Exodus wallet, 1AEdg), but with a slightly higher fee of 1333 sats/byte:
https://blockchain.info/tx/6513d2f741f0be851b1e400d8a28fc038f0f305dee19a553083e5ea89db2c6d2This transaction was CONFIRMED.
Then on 27th November 2017, the change output from successful "6513d" transaction was attempted to be spent in this transaction:
https://bitaps.com/57bb8beed3e04db00c99e078327f465cb1dbfdd8ed64264cab4cb0bf7f1be78eAgain, despite a 1321 sats/byte fee, this transaction is NOT confirmed??!?
This is important... as one of the outputs of this UNCONFIRMED transaction, was then used in the 21st DECEMBER transaction (which is currently showing as "conflicted" in your wallet):
https://bitaps.com/c356ab3c49929cdf34b0adb45851105cd1fafbb522b76c4ec461c52c1687d886With the previous transaction not being confirmed (and most likely dumped from the mempool after nearly a month)... this transaction will not confirm.
Then, the UNCONFIRMED output from the "ecb252" transaction on the 21st NOV was then attempted to be spent in your transaction on 22nd DECEMBER 2017 (which is currently showing as "conflicted" in your wallet):
https://bitaps.com/bbd0a1ac723ddbbf4449cc1d3cf29022158d38659455986e56b4d258d1f7fe09Obviously, that's impossible as the INPUT was already used in the transaction on 22nd Nov... so it will be "unconfirmed" forever.
And now we arrive at today... we can see you still have 3.147 BTC in
17qTnk8CaFRMYsidhFiDsgsi24acKD4NDrAnd as far as I can tell... there is no "missing" 2 BTC... they were "unconfirmed" inputs that were attempted to be double spent...
As for how to fix all this... I would recommend you do the following:
1. Make a couple of backups of your wallet.dat
2. Install latest version of Bitcoin Core and let it fully sync up
3. Using one of your "backup" wallet.dat's, start Bitcoin Core with the
-zapwallettxes commandline argument (This will remove ALL transactions from your wallet and then rescan the blockchain looking for "confirmed" transactions that belong to your wallet.)
4. If it doesn't rescan, shutdown Bitcoin Core and restart it with the
-rescan commandline argument.
After all this is completed, you should be able to see all the "true" transactions in your wallet history (ie. transactions that have been confirmed)... and you should also be able to see the 3.147 BTC (assuming that the "17qTn" address is contained within your wallet).
Best of luck.