<p>If you have the transaction ID you can get the raw hex transaction via:</p>

<pre><code>bitcoin-cli getrawtransaction &lt;txid&gt;
</code></pre>

<p>That will produce a rather long string <code>&lt;rawtx&gt;</code> which is the serialized transaction. You can then use</p>

<pre><code>bitcoin-cli sendrawtransaction &lt;rawtx&gt;
</code></pre>

<p>or any of the web interfaces that allow pushing a transaction (just search for <code>pushtx</code> and I'm sure you'll find a few providers). The raw transaction does not contain any private information. It is safe to publish, however services may attribute the transaction with your IP if you use them, so try <code>sendrawtransaction</code> first, which is the exact same behavior your client would use anyway.</p>

<p>Notice that your client will also automatically retry your wallet transactions every once in a while, so manual intervention may not be needed. It could be you haven't attached a large enough fee for the TX to be propagated in the network.</p>

CC BY-SA 3.0
2017-05-30T17:46:48.320Z
2017-05-30T17:46:48.320Z
cdecker
<p>Edit to the @cdecker answer.
I had the same problem using Bitcoin Core v22.0.0. My transaction wasn't send correctly because my proxy didn't work probably, but the transaction was already displayed in my wallet but never got sent to the bitcoin network. Even after fixing the network problem Bitcoin Core didn't resend the transaction.</p>
<p>If you're using the client version you can open the Console on the top and type the following without the bitcoin-cli to resend your transaction.</p>
<pre><code>getrawtransaction &lt;txid&gt;

sendrawtransaction &lt;rawtx&gt;
</code></pre>
<p><a href="https://i.sstatic.net/E6VH2.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/E6VH2.png" alt="enter image description here" /></a></p>

CC BY-SA 4.0
2021-12-12T22:15:21.350Z
2021-12-12T22:15:21.350Z
Sebastian
<p>i am running Bitcoin Core 0.14.1 on a  Centos6 Server.
I had several transactions (receive, send) in the last days, and everything was fine.</p>

<p>I always did my transaction with the bitcoin-cli sendtoaddress ADDRESS  AMOUNT ... and that worked fine. Always after some minutes i could see my unconfirmed transactions at Blockchain.info</p>

<p>But yesterday i made a new transaction same as always and i get an transactions id successfully, but i cant find my transaction in the Blockchain. And the receiver does not the transaction also.</p>

<p>What i have tried:</p>

<ul>
<li>I wait more than 24 hours ( but my transaction is not showing up in blockchain, and wasnt include in any block)</li>
<li><p>I turned off the IP Tables and make sure that the Wallet is connected to the network.</p></li>
<li><p>I stooped Bitcoin with bitcoin-cli stop and made an recan with bitcoind -rescan</p></li>
<li>I stooped Bitcoin with bitcoin-cli stop and made an recan with bitcoind -zapwallettxes</li>
<li>I deleted the memorypool.dat in .bitcoin directory</li>
<li>I reload the complete Blockchain</li>
</ul>

<p>Who has the solution?</p>

CC BY-SA 3.0
2017-05-27T20:32:11.117Z
What are you trying to achieve: Resending or recovering? Is the transaction still showing as unconfirmed on your server? Did the transaction get malleated and confirmed? Have you checked whether the transaction's inputs are still in your wallet? Did you delete the mempool file and do `-zapwallettxes` in the same go?
Murch
CC BY-SA 3.0
2017-05-27T20:35:40.483Z
I've guessed at your goal to give the question a more speaking title. If I guessed wrong, please edit to improve. :)
Murch
CC BY-SA 3.0
2017-05-27T21:15:27.767Z
The amount is subtracted from my balance and its shown in my wallet as unconfirmed transaction. I want to resend it.
John Doe
<bitcoind><bitcoin-core><unconfirmed-transactions><sendtoaddress>
Transaction created with sendtoaddress didn't propagate to the network, how to resend?
John Doe
# Transaction created with sendtoaddress didn't propagate to the network, how to resend?

(Asked by: username_0 on 2017-05-27)

i am running Bitcoin Core 0.14.1 on a Centos6 Server.
I had several transactions (receive, send) in the last days, and everything was fine.

I always did my transaction with the bitcoin-cli sendtoaddress ADDRESS AMOUNT ... and that worked fine. Always after some minutes i could see my unconfirmed transactions at Blockchain.info

But yesterday i made a new transaction same as always and i get an transactions id successfully, but i cant find my transaction in the Blockchain. And the receiver does not the transaction also.

What i have tried:

* I wait more than 24 hours ( but my transaction is not showing up in blockchain, and wasnt include in any block)
* I turned off the IP Tables and make sure that the Wallet is connected to the network.
* I stooped Bitcoin with bitcoin-cli stop and made an recan with bitcoind -rescan
* I stooped Bitcoin with bitcoin-cli stop and made an recan with bitcoind -zapwallettxes
* I deleted the memorypool.dat in .bitcoin directory
* I reload the complete Blockchain

Who has the solution?

**Tags:** bitcoind, bitcoin-core, unconfirmed-transactions, sendtoaddress

> **Comments:**
> **username_1**: What are you trying to achieve: Resending or recovering? Is the transaction still showing as unconfirmed on your server? Did the transaction get malleated and confirmed? Have you checked whether the transaction's inputs are still in your wallet? Did you delete the mempool file and do `-zapwallettxes` in the same go?  
> **username_1**: I've guessed at your goal to give the question a more speaking title. If I guessed wrong, please edit to improve. :)  
> **username_0**: The amount is subtracted from my balance and its shown in my wallet as unconfirmed transaction. I want to resend it.  

---

## 2 answers

### Answer by username_2 on 2017-05-30. Score: 4

If you have the transaction ID you can get the raw hex transaction via:

```
bitcoin-cli getrawtransaction <txid>

```

That will produce a rather long string `<rawtx>` which is the serialized transaction. You can then use

```
bitcoin-cli sendrawtransaction <rawtx>

```

or any of the web interfaces that allow pushing a transaction (just search for `pushtx` and I'm sure you'll find a few providers). The raw transaction does not contain any private information. It is safe to publish, however services may attribute the transaction with your IP if you use them, so try `sendrawtransaction` first, which is the exact same behavior your client would use anyway.

Notice that your client will also automatically retry your wallet transactions every once in a while, so manual intervention may not be needed. It could be you haven't attached a large enough fee for the TX to be propagated in the network.


---

### Answer by username_3 on 2021-12-12. Score: 0

Edit to the @username_2 answer.
I had the same problem using Bitcoin Core v22.0.0. My transaction wasn't send correctly because my proxy didn't work probably, but the transaction was already displayed in my wallet but never got sent to the bitcoin network. Even after fixing the network problem Bitcoin Core didn't resend the transaction.

If you're using the client version you can open the Console on the top and type the following without the bitcoin-cli to resend your transaction.

```
getrawtransaction <txid>

sendrawtransaction <rawtx>

```

[![enter image description here](https://i.sstatic.net/E6VH2.png)](https://i.sstatic.net/E6VH2.png)


---

