Quote from: eightbits on February 09, 2017, 02:57:21 PM

~That is very strange indeed. ~

This is only strange until you know what really happened. i explained it above too.

you received the transaction but your database (the blockchain_headers file) didn't have it because you were out of sync and had to download the rest of the headers. the last block height you had must have been anything lower than or equal to 452191 so your wallet announced it as unconfirmed.

but as soon as you downloaded the rest of the block headers and was caught up, your problem was solved. now when your wallet checks the database it sees your transaction (b84e73ee4e76....) is fount on block 452192 and based on how deep it is, you wallet announces the number of confirmation.