Transaction stuck, blockchain.info can't find it

jenga

newbie

Activity: 26

Merit: 0

Ok i managed to sync with pruning enabled. As soon as it finished i checked on blockchain again and to my surprise the transaction went through.

Quote from: XCASH on August 17, 2016, 04:56:41 PM

It probably needs rebroadcasting.

Quote from: ranochigo on August 16, 2016, 10:44:53 AM

Nodes do not relay invalid transactions, eg. Inputs that conflicts with another inputs of a transaction in their mempool or block database. This might be the case where the nodes that you relayed it to found it invalid and decided not to relay at all. Blockchain.info do display transactions that are conflicted if they know it.

Not sure if it had to do anything with the syncing process or just a matter of waiting a bit longer to rebroadcast. Also had to move the data folder to another partition so maybe that helped too somehow. Next time i'll attempt a higher fee anyway.

Quote from: achow101 on August 16, 2016, 09:58:22 AM

Then follow the instructions at http://www.achow101.com/2016/07/Bitcoin-Core-Troubleshooting#stuck-tx to fix your problem.

tried abandontransaction right after syncing but returned error code -5 and attempted zapwallettxes but doesn't work in pruning mode, but it's ok apparently i didn't actually need to run the commands xd

Thanks all for the support

XCASH

legendary

Activity: 929

Merit: 1000

Quote from: jenga on August 16, 2016, 09:48:13 AM

3 hours ago i committed this transaction:
552197fd89d241aa97d02846fc8f570ffe5e60e183c48c6e31848e521a719371-000
to: 1HcPgPjKsGFXwV7JKFCYFATHA8yKQbYo4T

in the client it says 0 unconfirmed with a fee of 0.00009567.
Blockchain.info cannot find this transaction, which is the worrying part.

This is not a valid transaction hash format, and blockchain.info won't recognise it.

552197fd89d241aa97d02846fc8f570ffe5e60e183c48c6e31848e521a719371-000

If the dash with three zeros at the end (-000) is removed it's a valid hash. This is valid, and blockchain.info accepts the format but says it can't find the transaction.

552197fd89d241aa97d02846fc8f570ffe5e60e183c48c6e31848e521a719371

I don't think your transaction is in the mempool because I couldn't find it when I searched here using the hash above, and the address you supplied.

https://bitcoinchain.com/mempool/

It probably needs rebroadcasting.

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Quote from: jenga on August 16, 2016, 10:37:17 AM

Quote from: achow101 on August 16, 2016, 09:58:22 AM

It's possible that your transaction is a double spend because you are not synced. This would make your transaction invalid and thus rejected.

You cannot cancel a transaction. Once it is broadcast, you cannot abort it.

However, you can remove the transaction from your wallet and resend it. First you need to sync your wallet. You can enable pruning to save space.

To enable pruning, add

Code:

prune=550

To the bitcoin.conf file in your data directory.

Then follow the instructions at http://www.achow101.com/2016/07/Bitcoin-Core-Troubleshooting#stuck-tx to fix your problem.

Ok didn't know pruning was a thing, now syncing everything up (the huge bump in space freed was weirdly satisfactory to watch, in case you were wondering), will report when finished (might take a while).
Even if the transaction was a double spent, shouldn't it show on blockchain anyway?

Nodes do not relay invalid transactions, eg. Inputs that conflicts with another inputs of a transaction in their mempool or block database. This might be the case where the nodes that you relayed it to found it invalid and decided not to relay at all. Blockchain.info do display transactions that are conflicted if they know it.

jenga

newbie

Activity: 26

Merit: 0

Quote from: ranochigo on August 16, 2016, 09:56:48 AM

Have you sent any transactions prior to that? Can you examine the transaction and see if you can see the unspent outputs in the address on a block explorer? It's best to not send transactions when the client is out of sync since the client can construct a transaction with spent outputs.

It's most likely an issue with the small fee. Run bitcoin core with -zapwallettxes and you can resend it.

I have sent many transactions before, last 2 months ago with similar amount and same fee.
I don't know how to examine a transaction as you said.
I'm now syncing the client. will report back when finished.

Quote from: achow101 on August 16, 2016, 09:58:22 AM

It's possible that your transaction is a double spend because you are not synced. This would make your transaction invalid and thus rejected.

You cannot cancel a transaction. Once it is broadcast, you cannot abort it.

However, you can remove the transaction from your wallet and resend it. First you need to sync your wallet. You can enable pruning to save space.

To enable pruning, add

Code:

prune=550

To the bitcoin.conf file in your data directory.

Then follow the instructions at http://www.achow101.com/2016/07/Bitcoin-Core-Troubleshooting#stuck-tx to fix your problem.

Ok didn't know pruning was a thing, now syncing everything up (the huge bump in space freed was weirdly satisfactory to watch, in case you were wondering), will report when finished (might take a while).
Even if the transaction was a double spent, shouldn't it show on blockchain anyway?

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

It's possible that your transaction is a double spend because you are not synced. This would make your transaction invalid and thus rejected.

You cannot cancel a transaction. Once it is broadcast, you cannot abort it.

However, you can remove the transaction from your wallet and resend it. First you need to sync your wallet. You can enable pruning to save space.

To enable pruning, add

Code:

prune=550

To the bitcoin.conf file in your data directory.

Then follow the instructions at http://www.achow101.com/2016/07/Bitcoin-Core-Troubleshooting#stuck-tx to fix your problem.

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Have you sent any transactions prior to that? Can you examine the transaction and see if you can see the unspent outputs in the address on a block explorer? It's best to not send transactions when the client is out of sync since the client can construct a transaction with spent outputs.

It's most likely an issue with the small fee. Run bitcoin core with -zapwallettxes and you can resend it.

jenga

newbie

Activity: 26

Merit: 0

3 hours ago i committed this transaction:
552197fd89d241aa97d02846fc8f570ffe5e60e183c48c6e31848e521a719371-000
to: 1HcPgPjKsGFXwV7JKFCYFATHA8yKQbYo4T

in the client it says 0 unconfirmed with a fee of 0.00009567.
Blockchain.info cannot find this transaction, which is the worrying part.

My bitcoin core is 14 weeks behind on blockchain syncronization, thats because i run out of space to store it (am poor lol).
I don't think thats the issue because months before i sent successfully while being unsyncronized, but i say it here anyway.

Should i wait? otherwise i will remove the transaction.

Topic: Transaction stuck, blockchain.info can't find it (Read 1552 times)