<blockquote>
<p><strong>How to avoid such situations?</strong></p>
</blockquote>
<p>You should be able to view the status of your first transaction in the <code>history</code> tab in Electrum. You can right click on a transaction to get some options to affect that transaction.</p>
<p>If using the Electrum daemon and command line you can use the <code>electrum history</code> command.</p>
<p>I suspect if you had seen a pending transaction, you wouldn't have created a duplicate.</p>
<blockquote>
<p><strong>Why did it do that?</strong></p>
</blockquote>
<p>I guess it held onto the first transaction until the network became available and then sent it - that would usually be the most useful and helpful approach for a wallet.</p>

CC BY-SA 4.0
2022-01-06T17:03:31.220Z
I use electrum daemon, not a wallet. Also it didn't throw to the network on restore connection but after I broadcasted the second transaction
Oleksandr IY
CC BY-SA 4.0
2022-01-06T22:12:11.080Z
OK, I think you'll find you get better answers if you include that sort of information in your question.
RedGrittyBrick
CC BY-SA 4.0
2022-01-06T15:06:03.163Z
2022-01-06T22:12:56.620Z
2022-01-06T22:12:56.620Z
RedGrittyBrick
<p>I had one strange situation. I created payment transaction, broadcasted it but electrum couldn't execute request due timeout, network weren't accessible. Then after 10 minutes I created one more transaction, broadcasted and  gone two transactions to the network  old and new one, but I expected only one new transaction to go out. How to avoid such situations? Why did it do that?</p>

<electrum>
doubled payment
Oleksandr IY
# doubled payment

(Asked by: username_0 on 2022-01-06)

I had one strange situation. I created payment transaction, broadcasted it but electrum couldn't execute request due timeout, network weren't accessible. Then after 10 minutes I created one more transaction, broadcasted and gone two transactions to the network old and new one, but I expected only one new transaction to go out. How to avoid such situations? Why did it do that?

**Tags:** electrum


---

## 1 answers

### Answer by username_1 on 2022-01-06. Score: 1

> **How to avoid such situations?**

You should be able to view the status of your first transaction in the `history` tab in Electrum. You can right click on a transaction to get some options to affect that transaction.

If using the Electrum daemon and command line you can use the `electrum history` command.

I suspect if you had seen a pending transaction, you wouldn't have created a duplicate.

> **Why did it do that?**

I guess it held onto the first transaction until the network became available and then sent it - that would usually be the most useful and helpful approach for a wallet.

> **Comments:**
> **username_0**: I use electrum daemon, not a wallet. Also it didn't throw to the network on restore connection but after I broadcasted the second transaction  
> **username_1**: OK, I think you'll find you get better answers if you include that sort of information in your question.  

---

