6 hours and 0 confirms!

[genjix]

At 1735 I made a transaction sending BTC to another offline wallet of mine using a computer with 0.3.19 beta. 8 connections and the full block chain.

At 2200 I downloaded 0.3.20 and opened that instead... Now it's 2250 and still 0 confirms...

Code:

    {
        "account" : "",
        "address" : "16xuHMEHQYVXTRJ6no5MivMVcCtPifEGsu",
        "category" : "send",
        "amount" : -65.48000000,
        "fee" : -0.00769472,
        "confirmations" : 0,
        "txid" : "fcf8d4487dc2d351879d2e2788e2b9554b80607c29e078f3b2b821496deb0f0e",
        "time" : 1298568918
    }

{
    "version" : 32001,
    "balance" : 0.00000000,
    "blocks" : 110231,
    "connections" : 2,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 36459.88692508,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1297624404,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

Can I retrieve my bitcoins now that this transaction seems to be borked?

[BitterTea]

Did you try using the -rescan switch? This forces it to scan the downloaded block chain for any transactions missing from the wallet.

[genjix]

Did you try using the -rescan switch? This forces it to scan the downloaded block chain for any transactions missing from the wallet.

Ha! thanks! I did that and immediately it shows up with 41 confirms.

Code:

    {
        "account" : "",
        "address" : "16xuHMEHQYVXTRJ6no5MivMVcCtPifEGsu",
        "category" : "send",
        "amount" : -65.48000000,
        "fee" : -0.00769472,
        "confirmations" : 41,
        "txid" : "fc6bd26302ca7362f5b32d87eaaeabf480a132f3639e397024b7a2cc3194e21d",
        "time" : 1298569457
    }

[theGECK]

Having a way in the GUI to rescan might be a good option, if this sort of thing happens, even infrequently. Make it user friendly for people to make sure that the transactions they thought were supposed to be there aren't "lost".

[Hal]

How did it happen though? Should be impossible unless you did more than you said.

[dingus]

I'm having this same problem. -rescan doesn't seem to do anything, as the transaction is still grey and has 0 confirms. It has been an hour or so and I have sent coins to myself to test it and that transaction worked, so I am not sure what to do now besides wait.

[M4v3R]

Same on my side:



One of these is from Bitcoin Faucet, other is from DeepBit. I've sent a couple of tx'es to myself before to test my new app. Could that trigger the problem?

Rescan switch didn't help.

Edit: I think it's worth noting that one of these addresses were generated by RPC command "getnewaddress". I don't see how this could affect confirmations though.

[bitminer]

I have the same problem:nobody confirmed the bitcoins I got from Bitcoin Faucet about 6 hours ago.

[rebuilder]

I had this a couple of times as well - transfers that showed up in my transaction list but never got confirmed until I forced a rescan of the block chain. I remember one was a send from MyBitcoin, don't remember what the other was. Weird stuff.

[dingus]

How do you force a rescan? ./bitcoin -rescan does nothing it seems.

[BitterTea]

How do you force a rescan? ./bitcoin -rescan does nothing it seems.

It should take longer than normal to open Bitcoin. Once it has opened, the rescan of the block chain is complete.

[Ricochet]

I have the same problem:nobody confirmed the bitcoins I got from Bitcoin Faucet about 6 hours ago.

How long has it been since you installed Bitcoin for the first time?  If this is your first time using it, it'll take several hours to download the already-existing block chain before you'll see the transaction appear.

[N12]

I’ve got the same problem, although it’s slush’s pool and not the faucet. I’ve got four transaction, the oldest of them being five hours old, unconfirmed now. Blockexplorer doesn’t show them either. Also, it has been lagging the whole day, needing a few hours to get only one confirm.

This means that the incoming transactions aren’t even in blocks yet and it’s not just me. Why?

[theymos]

Try adding a fee to a new transaction to see if it's a fee problem.

[gohan]

I'm having this same problem. -rescan doesn't seem to do anything, as the transaction is still grey and has 0 confirms.

This happened to me yesterday while switching wallets. -rescan worked only once, and then new transactions just started hanging at 0 for both wallets, for both sending and receiving. The transactions were in the block chain. Re-downloading the chain worked, but it was an unnecessary load on the network, -rescan should have done just the same. I'm keeping the old databases but I don't know what to look for. My guess was that the downloaded block chain was somehow corrupted, but a newly downloaded chain also only worked for the wallet I downloaded it for and not the other, even with -rescan.

[Mike Hearn]

Debug logs would help here.