<p>Bitcoin Core (bitcoind and Bitcoin-Qt's new name) v0.9 will deal much better with these conflicting transactions within one wallet.</p>

<p>It will keep showing both, but the non-confirming one will be marked "conflicted" with -1 confirmations, will not be rebroadcasted, and won't be considered to have spendable outputs.</p>

CC BY-SA 3.0
2014-03-09T11:48:55.163Z
Good news! Thank you! My understanding is that these conflicts occurred because of malleability, can please you confirm? And where can I see the planned release date for v0.9? I looked everywhere and can't find it.
Emre K.
CC BY-SA 3.0
2014-03-09T12:04:18.040Z
It looks like the result of malleability indeed. The release data for 0.9: "when it is ready". However, we already have a release candidate 2. Maybe it takes 1 or 2 more candidates.
Pieter Wuille
CC BY-SA 3.0
2014-03-09T13:53:32.280Z
Thanks again. I'm surprised this effect of malleability on Bitcoin Core isn't mentioned anywhere else. Except for Gavin Andresen's blog post which briefly mentions some coins might get stuck.
Emre K.
CC BY-SA 3.0
2014-03-09T11:42:04.083Z
2014-03-09T11:42:04.083Z
Pieter Wuille
<p>Have you tried the following?</p>

<ol>
<li>Dump all your private keys (<code>dumpprivkey</code>). Be sure to get all your receiving and change addresses. Back up wallet.dat just in case something bad happens.</li>
<li>Delete wallet.dat.</li>
<li>Open up bitcoin-qt again. It should create a new wallet.dat. Now go into the console and run <code>importprivkey</code> on each of those private keys.</li>
</ol>

CC BY-SA 3.0
2014-03-09T10:08:53.750Z
I'm mainly trying to find out how and why this happened so that I can prevent it from happening again.
Emre K.
CC BY-SA 3.0
2014-03-09T09:07:16.353Z
2014-03-09T09:07:16.353Z
Tony
<p>Try issuing <code>getrawtransaction txid</code> with txid of the offending transaction. Then, issue <code>sendrawtransaction string</code> with the string outputted by the first command. You can possibly post this string there, or try using it in another wallet software, this can give you some information on this TX and maybe finally broadcast it.</p>

<p>If you want to get rid of this TX, you can backup your wallet, remove all files from your ~/.bitcoin directory or its equivalent (the directory containing the blockchain), redownload the blockchain (possibly using the bootstrap.dat) and import your backupped keys back.</p>

CC BY-SA 3.0
2014-03-08T12:17:12.627Z
Already tried both. Tried broadcasting the Tx through both my wallet and blockchain.info. BC won't broadcast saying inputs have already been spent. Which is true. And nothing happens when I do the same from inside my Bitcoin client. Copied wallet and redownloaded blockchain, transactions are still there. I think the funds are stuck until a fix is released by core devs. Gavin's posts about malleability on foundation's blog says some transactions might be stuck and that they need to update the software to fix it.
Emre K.
CC BY-SA 3.0
2014-03-04T12:32:59.697Z
2014-03-04T12:32:59.697Z
czaks
<p>I received two payments with the following transaction:</p>

<p><a href="https://blockchain.info/tx/12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0" rel="nofollow">https://blockchain.info/tx/12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0</a></p>

<p>On this transaction</p>

<p>1HT1vrdy2fegnVKaTE1rqsFzfPVDpiWYjf output receives 0.1341765 BTC and 19tj6SNnJqZqmDvMuhrjwPudX8qVcT392a output receives 0.27240743.</p>

<p>I have this transaction in my BitcoinQT client. It shows confirmed and everything is fine. The problem is that I have another transaction which has the same inputs and outputs with the above but a different TxID.</p>

<p>It has been stuck in my wallet unconfirmed for two weeks. BC.info does not show this transaction. Neither does any other online service. Below are the full details.</p>

<p>I have around 10 other transaction in my wallet like this. What is this?￼ Why is this happening?</p>

<pre><code>gettransaction 98ea1e0d4169af104fe36535a4615ab82086750323ce4e539b7d9c82707955f6
{
"amount" : 0.40658393,
"confirmations" : 0,
"txid" : "98ea1e0d4169af104fe36535a4615ab82086750323ce4e539b7d9c82707955f6",
"time" : 1392119952,
"timereceived" : 1392119952,
"details" : [
{
"account" : "520c7bb149ede83218f46c96",
"address" : "1HT1vrdy2fegnVKaTE1rqsFzfPVDpiWYjf",
"category" : "receive",
"amount" : 0.13417650
},
{
"account" : "520c7bb149ede83218f46c96",
"address" : "19tj6SNnJqZqmDvMuhrjwPudX8qVcT392a",
"category" : "receive",
"amount" : 0.27240743
}
]
}

gettransaction 12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0
{
"amount" : 0.40658393,
"confirmations" : 2490,
"blockhash" : "00000000000000007465867d49096a642c424ae015691c0b0f6280c3bc6de401",
"blockindex" : 78,
"blocktime" : 1392120874,
"txid" : "12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0",
"time" : 1392120874,
"timereceived" : 1392120896,
"details" : [
{
"account" : "520c7bb149ede83218f46c96",
"address" : "1HT1vrdy2fegnVKaTE1rqsFzfPVDpiWYjf",
"category" : "receive",
"amount" : 0.13417650
},
{
"account" : "520c7bb149ede83218f46c96",
"address" : "19tj6SNnJqZqmDvMuhrjwPudX8qVcT392a",
"category" : "receive",
"amount" : 0.27240743
}
]
}
</code></pre>

CC BY-SA 3.0
2014-03-04T10:35:51.110Z
Have you read https://bitcointalk.org/index.php?topic=35214.0?
Jori
CC BY-SA 3.0
2014-03-04T10:57:15.673Z
@Jori Yes I did. But there is a difference between sending a transaction that does not get confirmed and having a duplicate of a confirmed transaction with a different ID stuck in your wallet. I want to find out how this happened.
Emre K.
CC BY-SA 3.0
2014-05-22T17:07:11.297Z
@AntonAnsgar, Can you point us to your other transactions that are differing only in the TXID?
Pacerier
CC BY-SA 3.0
2014-05-22T19:18:26.193Z
Hi! This is actually resolved with v0.9 of bitcoin core. These transaction were result of malleability and they are now showing as Conflicted on Bitcoin Core. You will probably not be able to observe them from another copy of the blockchain.
Emre K.
<transactions><bitcoin-core><transaction-malleability>
Stuck duplicate transaction in BitcoinQT
Emre K.
# Stuck duplicate transaction in BitcoinQT

(Asked by: username_0 on 2014-02-25)

I received two payments with the following transaction:

<https://blockchain.info/tx/12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0>

On this transaction

1HT1vrdy2fegnVKaTE1rqsFzfPVDpiWYjf output receives 0.1341765 BTC and 19tj6SNnJqZqmDvMuhrjwPudX8qVcT392a output receives 0.27240743.

I have this transaction in my BitcoinQT client. It shows confirmed and everything is fine. The problem is that I have another transaction which has the same inputs and outputs with the above but a different TxID.

It has been stuck in my wallet unconfirmed for two weeks. BC.info does not show this transaction. Neither does any other online service. Below are the full details.

I have around 10 other transaction in my wallet like this. What is this?￼ Why is this happening?

```
gettransaction 98ea1e0d4169af104fe36535a4615ab82086750323ce4e539b7d9c82707955f6
{
"amount" : 0.40658393,
"confirmations" : 0,
"txid" : "98ea1e0d4169af104fe36535a4615ab82086750323ce4e539b7d9c82707955f6",
"time" : 1392119952,
"timereceived" : 1392119952,
"details" : [
{
"account" : "520c7bb149ede83218f46c96",
"address" : "1HT1vrdy2fegnVKaTE1rqsFzfPVDpiWYjf",
"category" : "receive",
"amount" : 0.13417650
},
{
"account" : "520c7bb149ede83218f46c96",
"address" : "19tj6SNnJqZqmDvMuhrjwPudX8qVcT392a",
"category" : "receive",
"amount" : 0.27240743
}
]
}

gettransaction 12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0
{
"amount" : 0.40658393,
"confirmations" : 2490,
"blockhash" : "00000000000000007465867d49096a642c424ae015691c0b0f6280c3bc6de401",
"blockindex" : 78,
"blocktime" : 1392120874,
"txid" : "12e487de6fd8d920446cd8663dc11977d185ceaa25b7c6f36921fb76e58875f0",
"time" : 1392120874,
"timereceived" : 1392120896,
"details" : [
{
"account" : "520c7bb149ede83218f46c96",
"address" : "1HT1vrdy2fegnVKaTE1rqsFzfPVDpiWYjf",
"category" : "receive",
"amount" : 0.13417650
},
{
"account" : "520c7bb149ede83218f46c96",
"address" : "19tj6SNnJqZqmDvMuhrjwPudX8qVcT392a",
"category" : "receive",
"amount" : 0.27240743
}
]
}

```

**Tags:** transactions, bitcoin-core, transaction-malleability

> **Comments:**
> **username_1**: Have you read https://bitcointalk.org/index.php?topic=35214.0?  
> **username_0**: @username_1 Yes I did. But there is a difference between sending a transaction that does not get confirmed and having a duplicate of a confirmed transaction with a different ID stuck in your wallet. I want to find out how this happened.  
> **username_2**: @AntonAnsgar, Can you point us to your other transactions that are differing only in the TXID?  
> **username_0**: Hi! This is actually resolved with v0.9 of bitcoin core. These transaction were result of malleability and they are now showing as Conflicted on Bitcoin Core. You will probably not be able to observe them from another copy of the blockchain.  

---

## 3 answers

### Answer by username_3 on 2014-03-09. Score: 1

Bitcoin Core (bitcoind and Bitcoin-Qt's new name) v0.9 will deal much better with these conflicting transactions within one wallet.

It will keep showing both, but the non-confirming one will be marked "conflicted" with -1 confirmations, will not be rebroadcasted, and won't be considered to have spendable outputs.

> **Comments:**
> **username_0**: Good news! Thank you! My understanding is that these conflicts occurred because of malleability, can please you confirm? And where can I see the planned release date for v0.9? I looked everywhere and can't find it.  
> **username_3**: It looks like the result of malleability indeed. The release data for 0.9: "when it is ready". However, we already have a release candidate 2. Maybe it takes 1 or 2 more candidates.  
> **username_0**: Thanks again. I'm surprised this effect of malleability on Bitcoin Core isn't mentioned anywhere else. Except for Gavin Andresen's blog post which briefly mentions some coins might get stuck.  

---

### Answer by username_4 on 2014-03-09. Score: 0

Have you tried the following?

1. Dump all your private keys (`dumpprivkey`). Be sure to get all your receiving and change addresses. Back up wallet.dat just in case something bad happens.
2. Delete wallet.dat.
3. Open up bitcoin-qt again. It should create a new wallet.dat. Now go into the console and run `importprivkey` on each of those private keys.

> **Comments:**
> **username_0**: I'm mainly trying to find out how and why this happened so that I can prevent it from happening again.  

---

### Answer by username_5 on 2014-03-04. Score: 0

Try issuing `getrawtransaction txid` with txid of the offending transaction. Then, issue `sendrawtransaction string` with the string outputted by the first command. You can possibly post this string there, or try using it in another wallet software, this can give you some information on this TX and maybe finally broadcast it.

If you want to get rid of this TX, you can backup your wallet, remove all files from your ~/.bitcoin directory or its equivalent (the directory containing the blockchain), redownload the blockchain (possibly using the bootstrap.dat) and import your backupped keys back.

> **Comments:**
> **username_0**: Already tried both. Tried broadcasting the Tx through both my wallet and blockchain.info. BC won't broadcast saying inputs have already been spent. Which is true. And nothing happens when I do the same from inside my Bitcoin client. Copied wallet and redownloaded blockchain, transactions are still there. I think the funds are stuck until a fix is released by core devs. Gavin's posts about malleability on foundation's blog says some transactions might be stuck and that they need to update the software to fix it.  

---

