Post
Topic
Board Bitcoin Technical Support
Re: (n/a)transaction appears after network drop out when i try to send bitcoin out
by
shorena
on 11/09/2015, 19:25:41 UTC
The conflict is that your wallet had a transaction that it doesn't see on the network. Go to Help > Debug Window and click on the console tab. Then type in zapwallettxs. I think that should fix the problem.

I tried but it says "Method not found (code -32601)" and nothing done.


AFAIK its not working from console, but needs to be given as parameter when bitcoin starts. It would remove the conflicted transaction, in fact it would remove all transactions and rescan the local blockchain. That might take a few hours depending on your system speed. I would guess that the transaction you created for 2.5 BTC is the one in conflict though. It would be removed the wallet would recognize the other for ~7 BTC and adjust the balance accordingly.

If you want to try it and your OS is Windows, do:

#1 close bitcoin core, make sure it did its closing thing.
#2 hit Win + R (it opens a window called run)
#3 enter c:\Program Files\Bitcoin\bitcoin-qt.exe -zapwallettxes=1
#4 confirm with "OK"

-snip-
Thank you very much for your help. yes it have been more than 2 days i tried to search all possible recovery action and i have waited 1 whole day for the blockchain data to be downloaded again Sad

The transaction ID of the top (conflicted) transaction: 0d9e5f24268e91359095376b7fd9c695c658eae1abe253cfb99e889f95a49457-000
raw transaction data: No information available about transaction (code -5)

The transaction ID of the (n/a) transaction: 09c0ae63f87a59b48e688fd69e4ee5ebb013656224568d2fb6a24b5d3214853a-000
raw transaction data:
-snip- raw data-


Hope this can help to find out what is wrong.

Well your wallet knows about 09c..., but not about 0d9... which is odd considering that you issued it, might be due to the restoration from backup. From the size and the number of inputs of the TX it looks like someone cleaned your wallet. Does anyone else have access to your wallet? Specifically at ~2015-09-07 07:39:50 or a little earlier.