-snip-
It is not possible for a TX to be "lost in limbo" for any amount of time.
The input no, the actual TX yes.
An input is always either spent or unspent. If an unspent input is part of an unconfirmed TX that has been accepted by the nodes then for all intensive purposes it is "spent pending confirmation"
While this is true if it is known to all the nodes, a TX may not be known to all nodes. The one in question does not show on blockchain.info [1], blockr [2] nor on blockexplorer [3] which makes me think that very few nodes know about it. While the explorers are not important I also think the miningnodes do not know about it, thus it would be impossible to confirm.
however if the TX does not confirm after 24 hours then the input will again be spendable.
Not if the client you are using "forget" it still can spend the input. Since the -rescan did not work, OPs bitcoin-core still has no idea it is actually able to spend the input of the missing TX.
Yea, chill for the moment. a year or so ago, I "lost" a transaction, I just figured it would eventually work itself out. it took about a week, but it did... So, give it a couple days before freaking out..
But it was well propagated, wasnt it? It would not advice panicking either, but I also think that just waiting is not enough.
re-scan didnot work! now im panicking!!! pleeaseee help. any suggestions?
I have read in the past that sometimes once is not enough. As I wrote above I dont think waiting is the way to go in your case. I personally would try at least one more -rescan because it does not take that much time. If that fails the next thing I would do is to launch with
-reindex. This will take more time as you are rebuilding the data in the chainstate folder, which holds the information about your unspend outputs (see [4]).
[1]
https://blockchain.info/address/1A5iCBMXPJF7esUssyaaeLpTocoyW2EK6n[2]
http://btc.blockr.io/address/info/1A5iCBMXPJF7esUssyaaeLpTocoyW2EK6n[3]
https://blockexplorer.com/address/1A5iCBMXPJF7esUssyaaeLpTocoyW2EK6n[4]
https://en.bitcoin.it/wiki/Data_directory
