Stuck Bitcoin-QT Transaction?

[nightengale]

I sent this out as my wallet was syncing, and now it seems to be stuck. The info on it is:

Status: 0/unconfirmed, broadcast through 9 nodes
Date: 2/23/14 11:18
To: 16sUE8RhUm2XqN6EYn8HiQzE3w5FiXrJrS
Debit: -1.00 BTC
Net amount: -1.00 BTC
Transaction ID: 7295099e476cd9e4b64a2ac51e6e76ec55cf06afc59a2358bf84af9ac01a41b4

Doesn't show up in Blockchain.info... Not broadcast to enough nodes I guess? I'm guessing I can't cancel this, so is there any way to rebroadcast, or... I'm hoping this coin isn't lost?

Thanks for any advice anyone can offer.

[nahtnam]

I sent this out as my wallet was syncing, and now it seems to be stuck. The info on it is:

Status: 0/unconfirmed, broadcast through 9 nodes
Date: 2/23/14 11:18
To: 16sUE8RhUm2XqN6EYn8HiQzE3w5FiXrJrS
Debit: -1.00 BTC
Net amount: -1.00 BTC
Transaction ID: 7295099e476cd9e4b64a2ac51e6e76ec55cf06afc59a2358bf84af9ac01a41b4

Doesn't show up in Blockchain.info... Not broadcast to enough nodes I guess? I'm guessing I can't cancel this, so is there any way to rebroadcast, or... I'm hoping this coin isn't lost?

Thanks for any advice anyone can offer.

I get the error "transaction not found". It should be returned to your account soon.

[bitcoin44me]

Wait the synchro and you will see if the transaction was cancelled or will proceed

[nightengale]

Sync finished soon thereafter but transaction is still stuck at broadcast thru 9 nodes...

[howzar]

Sync finished soon thereafter but transaction is still stuck at broadcast thru 9 nodes...

Try waiting a few more hours.

[nahtnam]

Sync finished soon thereafter but transaction is still stuck at broadcast thru 9 nodes...

Try waiting a few more hours.

Just wait 24 hours. Your BTC will be returned.

[Kiki112]

give it some time, check back tommorow and see what happens

[DannyHamilton]

You are getting a lot of bad advice from people who are just making random guesses.  They don't understand what is happening any more than you do.  Following advice from someone that doesn't understand the problem and is just making random guesses is a great way to waste time, and can be a good way to lose money as well.

The transaction still exists in your wallet, but it is no longer visible on the bitcoin network.  If your wallet is connected to peers and has synchronized the blockchain, then the next most likely reason for this would be that the wallet created a transaction that is no longer valid.  This can happen if the wallet attempts to spend the "change" from a transaction before the change creating transaction is confirmed.

To get a better idea of what has happened, issue the following command in the "Console" of the "Debug Window" under the "Help" menu:

Code:

getrawtransaction 7295099e476cd9e4b64a2ac51e6e76ec55cf06afc59a2358bf84af9ac01a41b4

Then post the result here.  This will get the original transaction from your wallet in the "raw" format that is typically broadcast to all peers in the bitcoin network.

We will then be able to decode that to find out what inputs the transaction is attempting to spend.  We can look those inputs up on the blockchain and find out why the transaction is no longer valid, and how you ended up with this problem.

[nightengale]

Thanks for the response DannyHamilton, that was good advice. I also got similarly good advice on Reddit -- if it helps anyone down the road:

Open bitcoin-qt
Click help/debug window
Open the console tab
Type getrawtransaction 7295099e476cd9e4b64a2ac51e6e76ec55cf06afc59a2358bf84af9ac01a41b4
This will dump a big string, paste in into blockchain.info/pushtx page and press send.

Thanks again!!!

[Chris_Sabian]

Thanks for the response DannyHamilton, that was good advice. I also got similarly good advice on Reddit -- if it helps anyone down the road:

Open bitcoin-qt
Click help/debug window
Open the console tab
Type getrawtransaction 7295099e476cd9e4b64a2ac51e6e76ec55cf06afc59a2358bf84af9ac01a41b4
This will dump a big string, paste in into blockchain.info/pushtx page and press send.

Thanks again!!!

I had the same issue - 5 hr and waiting for a sizable transcation + fee.  I followed these instructions and the transaction went through.   

[amandawhite61]

Okay. Cool.

[skrubalov]

I am having same issue, but when I paste the string in PusTX, it returns:

Code:

pushTX returned false. Inputs locked?

What shoud I do?

[DannyHamilton]

I am having same issue, but when I paste the string in PusTX, it returns:

Code:

pushTX returned false. Inputs locked?

What shoud I do?

Paste the string here so we can take a look at it and let you know what the problem is.

[skrubalov]

01000000035f90504209b8ceb52bb41e99ec805b655637ef54db25a26e520ad97c7849955e01000 0008b483045022033c3ed7183b2c82b39f9028f6eccdd7950a46b7d3eb2408aaa2d4c222f38a728 022100f07975f8e0b3092a3509c1fca92c8b4d4ebcf3f3d9d0eb36754c2847b8323c45014104a55 ae122dde8a0da3fc8bf8f8cf1c577af3e0afa93bcbeefe2992ebd2e21224164b669dd9dd278decb 025c73d89d78888e2575158e388e204a7c8790b83d9f32ffffffff9fd4080c3424c82a200dde1b8 bb8d099c0f37ba34136ad2489ec149e9b28890e0d0000008c49304602210099cd1df56ef56d404f ce7a36b93fc5a83e704604a33f411c64c7cbb9a96c187f0221008361d7eb73365862f5f2eaf1882 d563a589477c85f1ffb742eb6e1bb01071422014104c9eb0121abfae01b7c0a50d9f33c76522a29 581050e259069b4535dfa896b4ca5ec7561a010faa5112f3c07021ade1b17b66276e6e2e60862ea 6257e8aefec15ffffffff1393ad08bc6dfd77ce6cbad31dd39f2049614b9f84c5fe4a4fb138ef27 5fb09e130000008a47304402200f4caa01db1dbc00963d3a3462f3ca143a786ca5b632d48d1dea3 b4dd1cca0140220097ffeb14fe9950bb002a80eb4d192834c3c16fe14ed40111ac599375d6ea468 014104c9eb0121abfae01b7c0a50d9f33c76522a29581050e259069b4535dfa896b4ca5ec7561a0 10faa5112f3c07021ade1b17b66276e6e2e60862ea6257e8aefec15ffffffff0280969800000000 001976a914f77086feabeedf663f21baabb79c250820be2b3388acb1d21c00000000001976a9144 51bd6821c3155716ef8fd0fe6e36c3369a889b588ac00000000

10x

[Foxpup]

01000000035f90504209b8ceb52bb41e99ec805b655637ef54db25a26e520ad97c7849955e01000 0008b483045022033c3ed7183b2c82b39f9028f6eccdd7950a46b7d3eb2408aaa2d4c222f38a728 022100f07975f8e0b3092a3509c1fca92c8b4d4ebcf3f3d9d0eb36754c2847b8323c45014104a55 ae122dde8a0da3fc8bf8f8cf1c577af3e0afa93bcbeefe2992ebd2e21224164b669dd9dd278decb 025c73d89d78888e2575158e388e204a7c8790b83d9f32ffffffff9fd4080c3424c82a200dde1b8 bb8d099c0f37ba34136ad2489ec149e9b28890e0d0000008c49304602210099cd1df56ef56d404f ce7a36b93fc5a83e704604a33f411c64c7cbb9a96c187f0221008361d7eb73365862f5f2eaf1882 d563a589477c85f1ffb742eb6e1bb01071422014104c9eb0121abfae01b7c0a50d9f33c76522a29 581050e259069b4535dfa896b4ca5ec7561a010faa5112f3c07021ade1b17b66276e6e2e60862ea 6257e8aefec15ffffffff1393ad08bc6dfd77ce6cbad31dd39f2049614b9f84c5fe4a4fb138ef27 5fb09e130000008a47304402200f4caa01db1dbc00963d3a3462f3ca143a786ca5b632d48d1dea3 b4dd1cca0140220097ffeb14fe9950bb002a80eb4d192834c3c16fe14ed40111ac599375d6ea468 014104c9eb0121abfae01b7c0a50d9f33c76522a29581050e259069b4535dfa896b4ca5ec7561a0 10faa5112f3c07021ade1b17b66276e6e2e60862ea6257e8aefec15ffffffff0280969800000000 001976a914f77086feabeedf663f21baabb79c250820be2b3388acb1d21c00000000001976a9144 51bd6821c3155716ef8fd0fe6e36c3369a889b588ac00000000

10x

I think that's the wrong transaction. That's transaction ID 1da82bcaa7be41ca4c0c3fbc0fd35adc8d855e3af40be19323889fc41453a4a8, sending BTC0.1 to 1PZLhvDs8S7rhq349DHFjuXs2smSEttNUJ. In any case, my node had no problem pushing it. There's no fee, but none is needed (if you don't mind waiting a long time for confirmations), and all inputs are confirmed and not double-spent. I've no idea why blockchain.info seems to hate it.

[skrubalov]

Yes this is the right transaction.

[Foxpup]

Whoops, I got your transaction mixed up with OP's. Not enough caffeine. Anyway, there's absolutely nothing wrong with that transaction as far as I can tell; blockchain.info just hates you, I guess.