<p>When using sendrawtransaction if the hash is generated but not propagated, then first I would assume that bitcoind retry mechanism will eventually send to the network. </p>

<p>On build 8.99 the transaction will go through, AcceptToMemoryPool. Which will validate the tx. So unless you see error TX rejected 22, which could be anything, as the validation is not yet reported. Then it's safe to assume you just need to wait.</p>

CC BY-SA 3.0
2014-01-09T20:16:48.760Z
Only if the transaction applies to your own wallet, will it be rebroadcast. Sendrawtransaction behaves exactly as if the transaction was received from the network.
Pieter Wuille
CC BY-SA 3.0
2014-04-09T22:59:12.613Z
@PieterWuille, Does this mean you should keep sending a transaction through sendrawtransaction until it appears on another node, or even in a block? Or would this be a bad practice and overload the network unnecessarily?
Mark
CC BY-SA 3.0
2017-05-31T00:27:28.393Z
@Mark Sending invalid transactions (e.g., double-, quadruple-, etc. -spending) would increase your node's banscore; see [this](https://bitcoin.stackexchange.com/a/44218/4334).
Geremia
CC BY-SA 3.0
2013-12-10T17:47:46.500Z
2013-12-10T17:47:46.500Z
serialb
<p>Could it be as simple as not having confirmations? BlockExplorer seems to keep it's own block database, that's only updated when a new block is reported. Your transaction won't immediately appear there. </p>

<p>Perhaps run <code>less ~/.bitcoin/debug.log</code> and do SHIFT + F to track for new logs. Once you submit your transaction, watch for errors which hint at the reason for failure.</p>

<p>If possible, try verifying it's not being broadcast by using a second node. If it's running with the txindex=1 flag, you can do <code>bitcoin-cli getrawtransaction &lt;txid&gt; 1</code> on arbitrary, non-wallet transactions. It should be possible after just a few seconds. </p>

CC BY-SA 3.0
2015-05-05T12:58:13.383Z
2015-05-05T12:58:13.383Z
karimkorun
<p>I'm on testnet, I've created a raw tx and I'm using bitcoind. I've confirmed that the hex is formed correctly and signrawtransaction returns complete:true.</p>

<p>After I've run bitcoind sendrawtransaction raw_tx I get a hash returned, however when I look at <a href="http://blockexplorer.com" rel="nofollow">http://blockexplorer.com</a> the hash cannot be found.</p>

<p>I'm definitely on testnet.</p>

<p>Can anyone suggest any ideas?</p>

<raw-transaction>
sendrawtransaction creates hash but does not propogate to the network
serialb
# sendrawtransaction creates hash but does not propogate to the network

(Asked by: username_0 on 2013-11-28)

I'm on testnet, I've created a raw tx and I'm using bitcoind. I've confirmed that the hex is formed correctly and signrawtransaction returns complete:true.

After I've run bitcoind sendrawtransaction raw\_tx I get a hash returned, however when I look at <http://blockexplorer.com> the hash cannot be found.

I'm definitely on testnet.

Can anyone suggest any ideas?

**Tags:** raw-transaction


---

## 2 answers

### Answer by username_0 on 2013-12-10. Score: 2

When using sendrawtransaction if the hash is generated but not propagated, then first I would assume that bitcoind retry mechanism will eventually send to the network.

On build 8.99 the transaction will go through, AcceptToMemoryPool. Which will validate the tx. So unless you see error TX rejected 22, which could be anything, as the validation is not yet reported. Then it's safe to assume you just need to wait.

> **Comments:**
> **username_1**: Only if the transaction applies to your own wallet, will it be rebroadcast. Sendrawtransaction behaves exactly as if the transaction was received from the network.  
> **username_2**: @username_1, Does this mean you should keep sending a transaction through sendrawtransaction until it appears on another node, or even in a block? Or would this be a bad practice and overload the network unnecessarily?  
> **username_3**: @username_2 Sending invalid transactions (e.g., double-, quadruple-, etc. -spending) would increase your node's banscore; see [this](https://bitcoin.stackexchange.com/a/44218/4334).  

---

### Answer by username_4 on 2015-05-05. Score: 0

Could it be as simple as not having confirmations? BlockExplorer seems to keep it's own block database, that's only updated when a new block is reported. Your transaction won't immediately appear there.

Perhaps run `less ~/.bitcoin/debug.log` and do SHIFT + F to track for new logs. Once you submit your transaction, watch for errors which hint at the reason for failure.

If possible, try verifying it's not being broadcast by using a second node. If it's running with the txindex=1 flag, you can do `bitcoin-cli getrawtransaction <txid> 1` on arbitrary, non-wallet transactions. It should be possible after just a few seconds.


---

