There would be nice if there was some info in the client that the transaction actually was broadcast to the network, and it's status. I might file a feature request on this one. At the moment I have 3 transactions that are "0/unconfirmed".
As long as it's noted as "0/unconfirmed" and I have successfully both received and sent BTC during this time, I find it a bit odd.
But I'll just wait some more and see.
Also I have been using different client versions (whithout meaning to) on my wallet recently. I suspect there might be a bug that causes this issue. I got some warning about possible double spending, and I don't know if this will prevent the client from retrying sending the transactions out to the network. There's been no double spending, just running 0.3.21-beta and 0.3.20.01 both on the same data directory AppData/Roaming/Bitcoin.
I tought that including a fee would speed up transfer of a transaction?
As it is now I have two transfers with 0.1 fee waiting, and one with no fee (perhaps I sent that with the older client?)
So this is the status now:http://imageshack.us/photo/my-images/703/mining2.png/
Frankly I am concerned there might be incompabilities between different bitcoin client versions that will cause problems, since I've had two different clients working on my data-directory as stated above.
The transfer of 4.81 BTC includes a fee of 0.1 and is newly made coins, I understand these takes longer to process in the network?
So what I am really worried about is that there might be some protocol or client issue. This is not a lot of money, but it would not have been fun to have this happen to a larger amount of BTC. But according to what the topic starter wrote, perhaps I should just wait more. Then we will see, I will keep you updated.