<p>There's a sort of hatred against satoshi dice lately.  The feeling is that satoshi dice clogs up the transaction record with lots of small transactions.  Some of the bigger mining pools have started to refuse the transactions.</p>

<p>Rescan and your other steps should have fixed everything, though.</p>

<p>Without including the sending address in your question, it's difficult to track the bitcoins.  My only thought is that you can try to re-spend the coins on yourself and maybe they'll return.  The easiest way to do this might be to extract the public and private key of the address that sent the coins and put those in a wallet in blockchain.info .  </p>

<p>To do this, go to the console of your bitcoin client and type</p>

<pre><code>walletpassphrase &lt;your password&gt; 20
dumpprivkey &lt;the address that sent the coins&gt;
walletlock
</code></pre>

<p>Open a new wallet at blockchain.info and use the Import/Export function to import that private key.  blockchain.info will show your new balance.</p>

<p>That private key is your coins.  Don't tell it to anyone.  The address, however, isn't a big secret.</p>

CC BY-SA 3.0
2013-04-09T10:04:46.937Z
Thank you for the advice. I just went through the suggested steps, but the new wallet at blockchain.info shows a balance of 0 BTC after importing my private key (which isn't true). My sending address for this transaction was 1EczFVtHbPmEUXPHEHrZYUp4T5dDxbvhU6 by the way. If you have a suggestion what else I could do, I would be delighted.
**Update** I sent all my leftover bitcoins to the new Blockchain address and they vanished unpropagated, telling me: Status: 0/unconfirmed, broadcast through 30 nodes. Maybe Bitcoin isn't for me.
DentalFloss
CC BY-SA 3.0
2013-04-09T11:36:42.327Z
Looking here: https://blockchain.info/address/1EczFVtHbPmEUXPHEHrZYUp4T5dDxbvhU6 I see that you played satoshi dice most recently and the money was sent to this address: 13a3h9eCFm5uUyPQv7dmxUAwscfo231Xiw .  That should be one of your addresses and there's money in there.  See if you can find that private address using the same technique that I showed you before.
Eyal
CC BY-SA 3.0
2013-04-09T11:47:18.457Z
Also get the private key of these addresses using the same process: 1NNra1wt5p9ai1Qye7Tq3xgV7yjDWFRvDi and 14D1nGhEzuG8UVcfCQVL6TB9jyS7Qwf61p .  Everytime you spend bitcoins, the money in the wallet that you don't spend goes to a new address, so your wallet file has *tons* of addresses.  You can list them all with this command: listaddressgroupings.  This is a python script to extract all your address private keys for import to blockchain.info: http://bitcoin.stackexchange.com/questions/4469/extract-private-keys-from-bitcoin-wallet
Eyal
CC BY-SA 3.0
2013-04-09T13:47:30.227Z
pywallet.py and importing the dump on blockchain.info did the job. Thank you so, so much. I got all my bitcoin back. I have to say though, I lost a good amount of faith in this system after this whole ordeal.
DentalFloss
CC BY-SA 3.0
2013-04-09T22:12:50.510Z
I'm still surprised that -rescan didn't solve the problem.  If you want, open a wallet at blockchain.info and transfer there.  They did a good job on making bitcoin painless.
Eyal
CC BY-SA 3.0
2013-04-08T18:33:08.883Z
2013-04-08T18:33:08.883Z
Eyal
<p>I made a transaction 2 days ago, (using BitcoinQT 0.8.1-beta on MacOS X) that didn't propagate. I can't find the transaction on blockexplorer or blockchain.info (or anywhere else for that matter) yet. The transaction just sits there in the client, unconfirmed and gobbled up my Bitcoins. The transfer required me to pay a tx fee that I gladly paid.</p>

<pre><code>Status: 0/unconfirmed
Date: 06.04.13 22:01
To: Satoshi Dice 78% 1dicec9k7KpmQaA8Uc8aCCxfWnwEWzpXE
Debit: -0.40 BTC
Transaction fee: -0.0005 BTC
Net amount: -0.4005 BTC
Transaction ID: 10cfa399f5c0a3c6a36e9678ae7c87af95f38899cfe21c7bd76caebd11a2919b
</code></pre>

<p>What I did thus far</p>

<ul>
<li>I let the client sit on the network for a couple of hours, hoping for it to re-send the transaction.</li>
<li>I found this <a href="https://bitcoin.stackexchange.com/questions/1161/how-to-debug-a-long-0-unconfirmed-status-in-the-bitcoin-client">debug thread</a> that suggested to use -rescan, which I did to no avail. </li>
<li>Then I backed up and deleted all data except the wallet to redownload the blockchain - which also failed to change anything.</li>
<li>I used the gui console to do a lookup and resend of the transaction using getrawtransaction / sendrawtransaction that resulted in the error below</li>
</ul>

<p>Error:</p>

<pre><code>getrawtransaction 10cfa399f5c0a3c6a36e9678ae7c87af95f38899cfe21c7bd76caebd11a2919b 1
No information available about transaction (code -5)

sendrawtransaction 10cfa399f5c0a3c6a36e9678ae7c87af95f38899cfe21c7bd76caebd11a2919b
TX decode failed (code -22)
</code></pre>

<p>Now I am wondering what went wrong and what steps to take next.</p>

<p>I am aware that similar questions have been posted before, but I think this instance is different because I feel I already exhausted the debug instructions provided in the debug thread. I apologize if I missed anything.</p>

<transactions><unconfirmed-transactions>
Unconfirmed transaction for 2 days despite network fees, rescans and redownload
DentalFloss
# Unconfirmed transaction for 2 days despite network fees, rescans and redownload

(Asked by: username_0 on 2013-04-08)

I made a transaction 2 days ago, (using BitcoinQT 0.8.1-beta on MacOS X) that didn't propagate. I can't find the transaction on blockexplorer or blockchain.info (or anywhere else for that matter) yet. The transaction just sits there in the client, unconfirmed and gobbled up my Bitcoins. The transfer required me to pay a tx fee that I gladly paid.

```
Status: 0/unconfirmed
Date: 06.04.13 22:01
To: Satoshi Dice 78% 1dicec9k7KpmQaA8Uc8aCCxfWnwEWzpXE
Debit: -0.40 BTC
Transaction fee: -0.0005 BTC
Net amount: -0.4005 BTC
Transaction ID: 10cfa399f5c0a3c6a36e9678ae7c87af95f38899cfe21c7bd76caebd11a2919b

```

What I did thus far

* I let the client sit on the network for a couple of hours, hoping for it to re-send the transaction.
* I found this [debug thread](https://bitcoin.stackexchange.com/questions/1161/how-to-debug-a-long-0-unconfirmed-status-in-the-bitcoin-client) that suggested to use -rescan, which I did to no avail.
* Then I backed up and deleted all data except the wallet to redownload the blockchain - which also failed to change anything.
* I used the gui console to do a lookup and resend of the transaction using getrawtransaction / sendrawtransaction that resulted in the error below

Error:

```
getrawtransaction 10cfa399f5c0a3c6a36e9678ae7c87af95f38899cfe21c7bd76caebd11a2919b 1
No information available about transaction (code -5)

sendrawtransaction 10cfa399f5c0a3c6a36e9678ae7c87af95f38899cfe21c7bd76caebd11a2919b
TX decode failed (code -22)

```

Now I am wondering what went wrong and what steps to take next.

I am aware that similar questions have been posted before, but I think this instance is different because I feel I already exhausted the debug instructions provided in the debug thread. I apologize if I missed anything.

**Tags:** transactions, unconfirmed-transactions


---

## 1 answers

### Answer by username_1 on 2013-04-08. Score: 1 | Accepted answer

There's a sort of hatred against satoshi dice lately. The feeling is that satoshi dice clogs up the transaction record with lots of small transactions. Some of the bigger mining pools have started to refuse the transactions.

Rescan and your other steps should have fixed everything, though.

Without including the sending address in your question, it's difficult to track the bitcoins. My only thought is that you can try to re-spend the coins on yourself and maybe they'll return. The easiest way to do this might be to extract the public and private key of the address that sent the coins and put those in a wallet in blockchain.info .

To do this, go to the console of your bitcoin client and type

```
walletpassphrase <your password> 20
dumpprivkey <the address that sent the coins>
walletlock

```

Open a new wallet at blockchain.info and use the Import/Export function to import that private key. blockchain.info will show your new balance.

That private key is your coins. Don't tell it to anyone. The address, however, isn't a big secret.

> **Comments:**
> **username_0**: Thank you for the advice. I just went through the suggested steps, but the new wallet at blockchain.info shows a balance of 0 BTC after importing my private key (which isn't true). My sending address for this transaction was 1EczFVtHbPmEUXPHEHrZYUp4T5dDxbvhU6 by the way. If you have a suggestion what else I could do, I would be delighted. **Update** I sent all my leftover bitcoins to the new Blockchain address and they vanished unpropagated, telling me: Status: 0/unconfirmed, broadcast through 30 nodes. Maybe Bitcoin isn't for me.  
> **username_1**: Looking here: https://blockchain.info/address/1EczFVtHbPmEUXPHEHrZYUp4T5dDxbvhU6 I see that you played satoshi dice most recently and the money was sent to this address: 13a3h9eCFm5uUyPQv7dmxUAwscfo231Xiw .  That should be one of your addresses and there's money in there.  See if you can find that private address using the same technique that I showed you before.  
> **username_1**: Also get the private key of these addresses using the same process: 1NNra1wt5p9ai1Qye7Tq3xgV7yjDWFRvDi and 14D1nGhEzuG8UVcfCQVL6TB9jyS7Qwf61p .  Everytime you spend bitcoins, the money in the wallet that you don't spend goes to a new address, so your wallet file has *tons* of addresses.  You can list them all with this command: listaddressgroupings.  This is a python script to extract all your address private keys for import to blockchain.info: http://bitcoin.stackexchange.com/questions/4469/extract-private-keys-from-bitcoin-wallet  
> **username_0**: pywallet.py and importing the dump on blockchain.info did the job. Thank you so, so much. I got all my bitcoin back. I have to say though, I lost a good amount of faith in this system after this whole ordeal.  
> **username_1**: I'm still surprised that -rescan didn't solve the problem.  If you want, open a wallet at blockchain.info and transfer there.  They did a good job on making bitcoin painless.  

---

