<p>When you do gettransaction, comment is available in the JSON. One need to set up callback for transaction and watch for his own comment.</p>

<p>I will update the answer with JSON dumps once I do enough testing.</p>

CC BY-SA 4.0
2019-09-04T16:48:27.853Z
2019-09-04T16:48:27.853Z
Nick
<p>In the event that <code>bitcoind</code> completes a transaction, but the RPC response is lost, the transaction details will still remain available. The wallet and transaction database is updated directly by <code>bitcoind</code>, and will be updated regardless of the RPC state.</p>

CC BY-SA 4.0
2019-09-04T15:43:27.660Z
Sure. But how I can access it?
Nick
CC BY-SA 4.0
2019-09-04T16:04:28.677Z
Just use the list transaction/wallet history RPC commands in a new RPC connection, the txs will be in your history. If there are N txs for the same amount to the same address simultaneously, does it really matter which txid is assigned to which tx? They are all fungible
Raghav Sood
CC BY-SA 4.0
2019-09-04T15:38:54.573Z
2019-09-04T15:38:54.573Z
Raghav Sood
<p>Suppose you call sendmany or sendtoaddress on bitcoind RPC.</p>

<p>Suppose the transaction is created and send to the network, but RPC time out and sender process unable to read the txid.</p>

<p>Suppose there are several send to same address with same btc amount.</p>

<p>How this can be tracked programically?</p>

<p>I know you can pass comment to each send but I am unsure how I can collect it programically.</p>

<bitcoin-cli>
how to track sendtoaddress / sendmany in case of network failure
Nick
# how to track sendtoaddress / sendmany in case of network failure

(Asked by: username_0 on 2019-09-04)

Suppose you call sendmany or sendtoaddress on bitcoind RPC.

Suppose the transaction is created and send to the network, but RPC time out and sender process unable to read the txid.

Suppose there are several send to same address with same btc amount.

How this can be tracked programically?

I know you can pass comment to each send but I am unsure how I can collect it programically.

**Tags:** bitcoin-cli


---

## 2 answers

### Answer by username_0 on 2019-09-04. Score: 0 | Accepted answer

When you do gettransaction, comment is available in the JSON. One need to set up callback for transaction and watch for his own comment.

I will update the answer with JSON dumps once I do enough testing.


---

### Answer by username_1 on 2019-09-04. Score: 1

In the event that `bitcoind` completes a transaction, but the RPC response is lost, the transaction details will still remain available. The wallet and transaction database is updated directly by `bitcoind`, and will be updated regardless of the RPC state.

> **Comments:**
> **username_0**: Sure. But how I can access it?  
> **username_1**: Just use the list transaction/wallet history RPC commands in a new RPC connection, the txs will be in your history. If there are N txs for the same amount to the same address simultaneously, does it really matter which txid is assigned to which tx? They are all fungible  

---

