Bitcoin Forum

I've sent this via the bitcoin client four hours ago:

Status: 0/unconfirmed, broadcast through 35 nodes
Date: 14/03/2013 16:37
To: 1Lz4jfrbJAXPimkqGyPLT5DvGZu3XVeD66
Debit: -10.00 BTC
Net amount: -10.00 BTC
Transaction ID: 18797f4a3eb77dc252cbf19784cfa910059bb23bd5e78ef0510a32cd048d18bf


It does not show on blockchain.info though. ("Sorry we could not find any blocks or transactions matching this hash").

I've read about transactions being slow recently, but *that* long?

No fee, so that's not going to help

Were any of the outputs smaller than 0.01 btc, by any chance? That (and no fee), is considered as spam, thus nodes will block it.

There is no need for a fee if coins are old enough.

I thought the client adds the fee automatically?

How can I check that?

Search for my thread about deleting 0/unconfirmed transactions. Also search for the Pywallet thread. You can delete the Txs from your wallet and -rescan it and your coins will come back.

Will do, thank you.



I did the same transaction again and it went in minutes:

Status: 1/unconfirmed, broadcast through 5 nodes
Date: 14/03/2013 20:52
To: 1Lz4jfrbJAXPimkqGyPLT5DvGZu3XVeD66
Debit: -10.00 BTC
Net amount: -10.00 BTC
Transaction ID: fe96f8421a24e4468ff579dbb32032bdb7cb45e823ee5fcb91a2561de75da957

Does the old transaction still show up in your client? In that case you didn't do the same transaction. Which client are you using?

Yes, it still sits there with 0 confirmations. What I meant to say is that I entered a new transaction the exact same way as I did the first one. Sorry to be unclear. They are two different transactions.

Just goes to show that the fees were not the issue this time, I guess.

They probably were. You did everything exactly the same, but chosen inputs to the transaction were different to those in the previous one. Since transaction priority entirely depends on transaction inputs, there can be a big difference. I'm pretty sure if you added a minimal transaction fee to the earlier transaction it would propagate normally.

In any case, you will have to find a way to remove that transaction from the client, since it's inputs are now frozen and you won't be able to use them again.

If the reference client (Bitcoin-Qt) is being used, then it shouldn't allow you to create a transaction that peers will refuse to relay.  If I had to guess, I'd guess that you received bitcoins that were lost to a double-spend and the client attempted to use those bitcoins in the transaction that you created.

More details would probably be needed to determine exactly what happened, but if the bitcoins were lost to a double-spend attack, then they probably won't show up in your wallet after the pywallet work and rescan.

That's what I thought, it is the official client 0.8.0

pywallet and rescan seems to have fixed it. Overall wallet balance remained the same however. Thanks cptmooseinc! Got a tip jar?

I can to provide more details, if you can tell me where to look for them.

13a2SNHdomYUS8cFqRCTPAQzi1PT63Eoig if you want to Newar. (;

Is your wallet still missing coins or is the balance as it should be after you tried to send the first Tx?? Whether or not it's the same is irrelevant. It's if it's correct is what matters.

Of course!

All looks good to me. Thanks again!

You're welcome! Thank you for the tip sir!!