<p>I found the answer on mailing list.</p>

<p><a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016441.html" rel="nofollow noreferrer">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016441.html</a></p>

<blockquote>
  <p>The <code>createrawtransaction</code> RPC will now accept an array or dictionary (kept for compatibility) for the <code>outputs</code> parameter. This means the order of transaction outputs can be specified by the client.</p>
</blockquote>

<p>According to the description, it should be the same order.</p>

CC BY-SA 4.0
2019-01-22T06:49:11.590Z
2019-01-22T06:49:11.590Z
atom
<p>Let say, when I set second parameter of <code>craterawtransaction</code> call as below</p>

<pre><code>[{"demoaddress1": 0.42}, {"demoaddress2": 1.00}]
</code></pre>

<p>Is it possible to occur that returned transaction's output is not ordered as same? like below</p>

<pre><code>[{"demoaddress2": 1.00}, {"demoaddress1": 0.42}]
</code></pre>

<json-rpc>
When using createrawtransaction, are the outputs ordered as they are presented within the request?
atom
# When using createrawtransaction, are the outputs ordered as they are presented within the request?

(Asked by: username_0 on 2019-01-22)

Let say, when I set second parameter of craterawtransaction call as below
[{"demoaddress1": 0.42}, {"demoaddress2": 1.00}]

Is it possible to occur that returned transaction's output is not ordered as same? like below
[{"demoaddress2": 1.00}, {"demoaddress1": 0.42}]

**Tags:** json-rpc


---

## 1 answers

### Answer by username_0 on 2019-01-22. Score: 2

I found the answer on mailing list.

<https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-October/016441.html>

> The `createrawtransaction` RPC will now accept an array or dictionary (kept for compatibility) for the `outputs` parameter. This means the order of transaction outputs can be specified by the client.

According to the description, it should be the same order.


---

