<p>Is one of the clients disconnected when you send payment with the other? This often happens to me when I send a transaction to the other OS on a dual-boot system, meaning the receiving client is down when the transaction is broadcast.</p>

<p>I'm guessing this happens because all nodes the client connects to when he comes online have already broadcast the transaction, so they won't send it again to him. He'll only get it as part of a block when it is found.</p>

CC BY-SA 3.0
2012-06-24T15:31:27.700Z
Nope. Both machines are up the whole time, and they have different IP addresses. The server is the one that takes a long time to see the transaction.
user1513
CC BY-SA 3.0
2012-06-24T11:51:19.183Z
2012-06-24T11:51:19.183Z
Meni Rosenfeld
<p>If the transaction is "spam-like" other nodes won't relay it.  This is to help protect the Bitcoin network from too many low priority transactions. </p>

<p>Was the transaction for a tiny amount? (e.g., under 0.01 BTC?) and no fee paid?  If so, that's kind of "spam-like".  I don't know the exact algorithm, but both of those are factors.</p>

CC BY-SA 3.0
2012-06-24T18:34:26.487Z
2012-06-24T18:34:26.487Z
Stephen Gornick
<p>I've noticed that sometimes, when I send Bitcoins from one client to another, the recipient client might not see the transaction, sometimes until it already has one or more confirmations. Both clients are connected to 30-40 nodes.</p>

CC BY-SA 3.0
2012-06-24T10:42:32.963Z
Only time I got that is when I was trying to experiment with double-spending against myself. Are both of your's Bitcoin clients up to date?
ThePiachu
CC BY-SA 3.0
2012-06-24T15:36:55.593Z
Both clients are up to date.
user1513
<transactions><network>
What might cause the Bitcoin client to take a long time to see a new, unconfirmed transaction?
user1513
# What might cause the Bitcoin client to take a long time to see a new, unconfirmed transaction?

(Asked by: username_0 on 2012-06-24)

I've noticed that sometimes, when I send Bitcoins from one client to another, the recipient client might not see the transaction, sometimes until it already has one or more confirmations. Both clients are connected to 30-40 nodes.

**Tags:** transactions, network

> **Comments:**
> **username_1**: Only time I got that is when I was trying to experiment with double-spending against myself. Are both of your's Bitcoin clients up to date?  
> **username_0**: Both clients are up to date.  

---

## 2 answers

### Answer by username_2 on 2012-06-24. Score: 3

Is one of the clients disconnected when you send payment with the other? This often happens to me when I send a transaction to the other OS on a dual-boot system, meaning the receiving client is down when the transaction is broadcast.

I'm guessing this happens because all nodes the client connects to when he comes online have already broadcast the transaction, so they won't send it again to him. He'll only get it as part of a block when it is found.

> **Comments:**
> **username_0**: Nope. Both machines are up the whole time, and they have different IP addresses. The server is the one that takes a long time to see the transaction.  

---

### Answer by username_3 on 2012-06-24. Score: 1

If the transaction is "spam-like" other nodes won't relay it. This is to help protect the Bitcoin network from too many low priority transactions.

Was the transaction for a tiny amount? (e.g., under 0.01 BTC?) and no fee paid? If so, that's kind of "spam-like". I don't know the exact algorithm, but both of those are factors.


---

