Transaction stuck at 0 conf - but blockchain confirmed already?

[vegeto079]

I have an incoming transaction that's 5 days old (March 08) that still says zero confirmations. When I right click it and press "view on blockchain.info" it shows that (currently) it has 942 confirmations. All of my other transactions going to the same address are fine, but this one is stuck in "unconfirmed" in the client, regardless of how confirmed the actual transaction seems to be.

Here's the transaction.

Thank you!

[etotheipi]

Look in the bottom-right corner of Armory, It should say (approx)  "Connected (290474 blocks)".

My guess is that it shows a number far less than 290,474.    Did you move your Bitcoin-Qt/bitcoind datadir recently?  When this happens, it's usually that someone puts Bitcoin-Qt in a different place, but Armory keeps reading the old, stale blockchain in the original directory.  So it will never see new blocks.   Just a hunch...

[vegeto079]

Thanks for the reply. Unfortunately that doesn't seem to be the issue: see this image, it semes to be up to date.

I haven't moved my data directory recently, in fact I haven't touched it for a very long time. The only recent thing I've done is create a new wallet, although up until this point everything was running smoothly (including those other transactions to the same wallet).

Here is the transaction info, if it helps.

I have Bitcoin-Qt running from syslinked directory, but Armory running from the default directory. I've not had any issues with that for a long time though; it's not a recent change.

[vegeto079]

Any help? The transaction is 10 days old and still held up with "zero confirmations" even though it's at 1689 now

[goatpig]

Need a log file at this point. This is a sync issue most likely, however verifiy it is the right address you have in your wallet ledger on the Armory side, and send up a log at support@bitcoinarmory.com with a link to this thread.

[jaebird]

This happened to me once. I cleared unconfirmed and rebuilt database and the transaction appeared. The behavior is what you described: Connected with current block height but 0 confirmations on an incoming transaction that was old and already deep in the blockchain.

[vegeto079]

This happened to me once. I cleared unconfirmed and rebuilt database and the transaction appeared. The behavior is what you described: Connected with current block height but 0 confirmations on an incoming transaction that was old and already deep in the blockchain.

Thank you, going to Help>Clear All Unconfirmed is what fixed the problem for me. The transaction is appearing as normal now. Cheers.