Quote from: mocacinno on Today at 05:24:16 PM

I'm happy you got things solved

Just for your info, there used to be a command "listreceivedbyaddress 0 true" that could be run from the console (either use bitcoin-cli from the commandline, or open a console in the bitcoin core gui implementation). I didn't check for more recent bitcoin core versions, but i'd be supprised if it was removed...

It's a safe command that should show all historically (and currently) funded addresses. The parameter "0" indicates that also addresses funded with unconfirmed transactions should be shown, and the parameter "true" indicates watchonly addresses should also be shown.

Thanks for your help .

Actually this is very strange.

I tried that command in both machines .
Listreceivedbyaddress 0 true then it shows
Both machines came up with the same address starting with 1 the legacy address with funding of the same amount.

However machine 2 came up with the address starting with 3 at the start with more coins inside?

But this seems so weird because on both machines the gui front page on the wallet shows received coins to the address starting with 3
Address.

Can sometimes addresses be missed out of a wallet.dat?

But if it was missed out how can the gui show it on the wallet front page ? I see that address starting with 3 on both wallets. Even though it is not there when I do the listreceivedbyaddress 0 true command.

Can a wallet dat saved at a different time miss out an address?
But if it did why would it show on the gui it received coins to that address on the wallet front page?

Machine 1 the most recently synced one shows coins recieved to an address starting with 3
But that command listreceivedbyaddress 0 true does not bring that up in the console.