<p>There is no way to know for sure which address is which.  This is part of the reason why some clients use a new address for change, for privacy; an observer will not be sure which coins now belong to whom.</p>

<p>There is no public timestamp recording when an address was created.  If one of the addresses has been used before and the other has not, this might suggest that the new one is for the change; but it could also be that both outputs are going to two different people, or that the sender is sending coins to herself and both addresses are "change".</p>

CC BY-SA 3.0
2013-11-01T18:52:26.980Z
okay, how does one send a transaction to two (or more) different people/addresses at the same time on purpose? I don't see any clients supporting this, is it something I can do in a command line sequence?
CQM
CC BY-SA 3.0
2013-11-01T23:08:37.040Z
Bitcoin-Qt certainly supports multiple destinations in a single transaction. The RPC interface of bitcoind also does, through `sendmany`.
Pieter Wuille
CC BY-SA 3.0
2013-11-01T18:07:54.817Z
2013-11-01T18:07:54.817Z
Nate Eldredge
<p>a lot of bitcoin clients now send change address balances back to the origin address, by default, to make it easier for people to keep track of their balances.</p>

<p>with this in mind, those transactions are easy to reveal which address is the origin, the destination and the change address.</p>

<p>Also this singles out transactions that do not behave this way, where the origin address splits the transaction into a real destination and a new change address and coins sit in both. Just from looking at the blockchain, how would one decide which address was the real destination and which one was the new change address. Would it be the timestamp each address was created or similarly when it was first revealed to have a transaction?</p>

<transactions><blockchain><address><timestamp><change>
distinguish change address from real origin<->destination
CQM
# distinguish change address from real origin<->destination

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

a lot of bitcoin clients now send change address balances back to the origin address, by default, to make it easier for people to keep track of their balances.

with this in mind, those transactions are easy to reveal which address is the origin, the destination and the change address.

Also this singles out transactions that do not behave this way, where the origin address splits the transaction into a real destination and a new change address and coins sit in both. Just from looking at the blockchain, how would one decide which address was the real destination and which one was the new change address. Would it be the timestamp each address was created or similarly when it was first revealed to have a transaction?

**Tags:** transactions, blockchain, address, timestamp, change


---

## 1 answers

### Answer by username_1 on 2013-11-01. Score: 1

There is no way to know for sure which address is which. This is part of the reason why some clients use a new address for change, for privacy; an observer will not be sure which coins now belong to whom.

There is no public timestamp recording when an address was created. If one of the addresses has been used before and the other has not, this might suggest that the new one is for the change; but it could also be that both outputs are going to two different people, or that the sender is sending coins to herself and both addresses are "change".

> **Comments:**
> **username_0**: okay, how does one send a transaction to two (or more) different people/addresses at the same time on purpose? I don't see any clients supporting this, is it something I can do in a command line sequence?  
> **username_2**: Bitcoin-Qt certainly supports multiple destinations in a single transaction. The RPC interface of bitcoind also does, through `sendmany`.  

---

