<p>If you call <code>listtransaction</code>, you should get a JSON array called <code>walletconflicts</code>.</p>

<p>If your transaction conflicts with another transaction in your mempool or with a transaction in a block, this <code>walletconflicts</code> array is filled with <code>n</code> transactions-id's that points to the tx that spends the same, conflicting inputs.</p>

<p><code>walletconflicts</code> is also present in <code>gettransaction</code></p>

CC BY-SA 3.0
2016-11-01T12:59:57.857Z
2016-11-01T12:59:57.857Z
Jonas Schnelli
<p>I use bitcoind's <code>Wallet</code> feature to manage my bitcoins.
Using json-rpc interface, how can I check that a transaction is a conflicted one? And, how can I get <code>txhash</code> of a transaction, that spends those same outputs and is confirmed(malleability situation)?</p>

<bitcoind><wallet><bitcoin-core><transaction-malleability>
Bitcoin Core 0.13 -- jsonrpc interface -- conflicted transactions
Yevhen
# Bitcoin Core 0.13 -- jsonrpc interface -- conflicted transactions

(Asked by: username_0 on 2016-11-01)

I use bitcoind's `Wallet` feature to manage my bitcoins.
Using json-rpc interface, how can I check that a transaction is a conflicted one? And, how can I get `txhash` of a transaction, that spends those same outputs and is confirmed(malleability situation)?

**Tags:** bitcoind, wallet, bitcoin-core, transaction-malleability


---

## 1 answers

### Answer by username_1 on 2016-11-01. Score: 3 | Accepted answer

If you call `listtransaction`, you should get a JSON array called `walletconflicts`.

If your transaction conflicts with another transaction in your mempool or with a transaction in a block, this `walletconflicts` array is filled with `n` transactions-id's that points to the tx that spends the same, conflicting inputs.

`walletconflicts` is also present in `gettransaction`


---

