Transaction didn't go through, blockchain unable to find it.

[Fabrizio89]

I paid the standard fee, but didn't wait for my client to sync with the network (was a couple of hours behind I used it the same morning), I don't know if this may be a problem. The transaction was sent yesterday at 2 pm.

I probably have the same problem this guy had, but nothing worked:
https://bitcointalk.org/index.php?topic=140558.0

I tried to use an older backup of my wallet (the balance is still missing, BTC0,6401), redownloading the blockchain, -rescan bitcoin-qt (0.85)... nothing worked so far. Is it possible that somehow someone doublespent my coins? I find this really hard to believe, but I can't find any other explanation.

This is the transaction ID: cbc49e0256b333e19ff945c0aa4d6c4d156f3d5b58a320cbd408fabd8caefb6c
If I try to https://blockchain.info/pushtx this is what I get: Unable To find all tx inputs: [03aee544260000db6f10e415e9d2dc03bcc3fe8d308297f06006a9dda59d8db5, dd7782618b7db9cd7f093f4d77660726436f8774ff2c37b7b01567287eb64e4f]

Would importing the wallet on the blockchain solve the problem? I'm not really comfortable in using web wallets.

Any idea?

[1714823443]

1714823443

[1714823443]

1714823443

[1714823443]

1714823443

[Kouye]

If you want the transaction to go out:
  If the transaction is actually showing in your QT history
    Then let the client catch up with the blockchain and your tx will be pushed eventually
  Else
    ExportImportPrivateKeys()
    Your balance is now right
    Wait for QT client to catch up with the blockchain
    Push your transaction again
Else
  If the transaction is actually showing in your QT history
    Backup your wallet
    Copy/Paste the tx id in a text editor
    Shut QT client down
    Use pywallet to remove the unwanted tx (using the id you previously pasted)
    Relauch QT client with the -rescan argument, and wait for it to catch up with the blockhain
    If you balance is still not right
      ExportImportPrivateKeys()
  Else
    ExportImportPrivateKeys()
     
 


ExportImportPrivateKeys()
If private keys count makes it impossible to do it key by key
  Bulk export your keys using pywallet
  Bulk import your keys to blockchain.info
  Send the coins from blockchain back to a newly created address of your local wallet
  (optional) Remove all the private keys from blockchain.info (a bit tedious, but possible)
Else
  Shutdown internet connection
  Create a new address and paste the public key to a text editor
  Backup your wallet
  Export your private keys one by one and paste them to a text editor
  Shutdown QT client
  Rename your wallet.dat
  Restart QT client
  Import your privates keys one by one
  Close text editor containing the private keys
  Restart internet connection
  Wait for QT client to catch up with the blockchain
  Send those coins back to the address you pasted in text editor




Hopefully I got that about right, I had a similar issue with balance not being right even after a rescan, and this worked for me.

[DannyHamilton]

This is the transaction ID: cbc49e0256b333e19ff945c0aa4d6c4d156f3d5b58a320cbd408fabd8caefb6c

Lets start with this so we can understand what happened to your wallet.

You've played around a bit with old backups of the wallet and re-downloading the blockchain, so I'm not even sure what state you have your wallet in any longer.

In the "Transactions" section of your wallet, does it show that transaction?

If so, please go to the "Console" in the "Debug Window" under the "Help" menu.

Type:

getrawtransaction cbc49e0256b333e19ff945c0aa4d6c4d156f3d5b58a320cbd408fabd8caefb6c

Post the resulting string of data here.  That will allow us to analyze the transaction and figure out what inputs it is attempting to spend.

Would importing the wallet on the blockchain solve the problem? I'm not really comfortable in using web wallets.

Probably not.

[Fabrizio89]

Thanks for your help Kouye, seems like it didn't work for me.

@Danny This is what I get:

01000000024f4eb67e286715b0b7372cff74876f43260766774d3f097fcdb97d8b618277dd00000 0006b48304502201871f8118579998d5092969c89b70498d64d48b0980d7131a379de334210e518 022100b020e349597d829cd5a992129bf8c03973f0cf366d515b38eff4daf7e2a331d301210285d 457564908cb06f38aec30047baf2de27e05ac6eea6381942e31922d6f75e7ffffffffb58d9da5dd a90660f09782308dfec3bc03dcd2e915e4106fdb00002644e5ae03010000006a47304402202ac22 bb3d88d270a9cb928c3703aeeb58cce8c8134c142b4becd862a0872f737022034feac8c3dabc7df db22a2af79b4753ae725b5b6772bdf86dad56c28245605f0012102559d9201f784e0f3692230383 dd099db5da6e1026892000ddd61223074537ad1ffffffff0243148a00000000001976a9143e59a8 b30a47630a93fa393894b22e5caa1ae12288ac0090d003000000001976a914a28a0232068387d6a b9fcd9befb09c34c784dc5a88ac00000000

Thanks again.

[DannyHamilton]

@Danny This is what I get:

Your wallet seems to believe that it has received two payments in the past that it thinks haven't been spent yet.

The first was:

Transaction ID dd7782618b7db9cd7f093f4d77660726436f8774ff2c37b7b01567287eb64e4f where it received 0.085 BTC at address 15MmNq226DyN3W8YmChJBvebRaRCWg6qvY from address 1AFTLpu3Dagva2ss6YBHyVEUw54L2Nj7DN on 2013-11-11 at approximately 18:27 UTC (you'll have to convert to your own timezone to know when the transaction occurred).

This payment has already been spent on 2013-11-14 at to address 1Pm55EBaAD3wjz2j2kjTNJcraNZMwJTU9X in transaction ID 98d7037e7f92921e3b5ef2989e24efa106d1f5cea651460fc02767ca4523034b, but for some reason this wallet appears to be unaware of that.  Therefore the wallet is still showing this 0.085 BTC as part of your balance and attempting to double-spend it in the transaction that you are asking about.

If you aren't aware of sending 0.0849 BTC to address 1Pm55EBaAD3wjz2j2kjTNJcraNZMwJTU9X at that time, then it is possible that someone got access to your private key and stole these bitcoins.

The second was:

Transaction ID 03aee544260000db6f10e415e9d2dc03bcc3fe8d308297f06006a9dda59d8db5 where it received at least 0.64549155 (and possibly a bit more).  This transaction does not appear to exist in the blockchain or on the bitcoin network at all.  Either it is a transaction that your wallet created and was unable to broadcast, or it is a transaction that someone else sent to you, which never confirmed and is no longer being broadcast by them.

To determine where this nonexistent transaction came from, we'll have to analyze it and see if you recognize any of the details.  Please now run

Code:

getrawtransaction 03aee544260000db6f10e415e9d2dc03bcc3fe8d308297f06006a9dda59d8db5

So we can see what transaction this is, where it came from, and when it showed up in your wallet.  If it is a corrupted transaction created by your wallet, we can try deleting it from your wallet to free up the bitcoins.  If it is a transaction you received from someone else that they are no longer broadcasting, then we can see if you recognize whom and you can contact them and ask them to re-send it.