Since 0.3.23, -rescan will also update unconfirmed transactions already in your wallet.
If you haven't upgraded to 0.3.23, I'd suggest to do so, and try starting it with -rescan on the command line.
Topic: Man... Bitcoin transactions not processing... the death of Bitcoin? (Read 1471 times)
July 03, 2011, 05:05:31 AM
If -rescan doesn't work, there's another function available called -purgetx which isn't in the default client but can rebuild your wallet.dat from the blockchain.
Let us know how it goes.
Let us know how it goes.
July 03, 2011, 04:50:03 AM
It's a problem with your client. Here's the transaction receiving your 0.15 BTC:
http://blockexplorer.com/t/4aAifH59fY
So... it's in the block chain, that's all that you need worry about from a financial point of view.
It's timestamp is 2011-06-22 19:33:48
So it took a fair few hours to be accepted.
Someone who is more expert than I on the black magic of the official client will have to suggest a solution. My guess would be something like "run it again with -rescan".
http://blockexplorer.com/t/4aAifH59fY
So... it's in the block chain, that's all that you need worry about from a financial point of view.
It's timestamp is 2011-06-22 19:33:48
So it took a fair few hours to be accepted.
Someone who is more expert than I on the black magic of the official client will have to suggest a solution. My guess would be something like "run it again with -rescan".
July 03, 2011, 04:10:54 AM
Your block count is wrong - its at 134502 now
Dude, honestly, posting worthless comments...what exactly is your purpose in this forum?His block count is correct, 30 minutes have passed since he posted this topic, it's fully possible for a few blocks to have been found.
July 02, 2011, 11:40:27 PM
Your block count is wrong - its at 134502 now
July 02, 2011, 11:36:04 PM
A few things you can check:
Check with block explorer that the transaction exists. (cue: google)
If you have an old backup, you could try deleting everything in your data directory, and copy back the old wallet.dat. Make sure you shut down the client first, and if you move or delete files, it's always good to make extra backups.
I had a similar problem to you, and I don't remember the details now, but it was solved by deleting everything in the data directory and inserting an old copy of the wallet.dat, then downloading the block chain again.
The data directory is in c:\users\youruser\appdata\roaming\bitcoin
Check with block explorer that the transaction exists. (cue: google)
If you have an old backup, you could try deleting everything in your data directory, and copy back the old wallet.dat. Make sure you shut down the client first, and if you move or delete files, it's always good to make extra backups.
I had a similar problem to you, and I don't remember the details now, but it was solved by deleting everything in the data directory and inserting an old copy of the wallet.dat, then downloading the block chain again.
The data directory is in c:\users\youruser\appdata\roaming\bitcoin
July 02, 2011, 11:17:12 PM
http://i319.photobucket.com/albums/mm480/theskewer/bitcoin.png
Pretty self-explanatory what the issue is, what with it being July 2nd...
Why hasn't it processed? Bitcoin is not going to be a viable client if it cannot process transactions within 24 hours...
Am I doing it wrong, or is the Bitcoin system failing me?
Pretty self-explanatory what the issue is, what with it being July 2nd...
Why hasn't it processed? Bitcoin is not going to be a viable client if it cannot process transactions within 24 hours...
Am I doing it wrong, or is the Bitcoin system failing me?
Jump to: