user74111: I'm having trouble performing the double-sha256 hash of the previous transaction, Step 3 in this explanation.
The previous transaction is: 
084fb53458bda42cf906dc2608fe962667188849e51e1dc13cd291cc13c97290
I've input the full transaction I want to perform into coinb.in as shown here, giving me a full transaction of:
01000000019072c913cc91d23cc11d1ee5498818672696fe0826dc06f92ca4bd5834b54f08010000001976a91460077bce1849cc2a41e2ccaa6ec575b3f5b70a9d88acffffffff0120a107000000000017a9144574085e1ef5432a6b09218f3b6ab6128f8eb2a58700000000
From what I understand, the double-sha256 of the previous tx here is:
9072c913cc91d23cc11d1ee5498818672696fe0826dc06f92ca4bd5834b54f08
However when I perform sha256 twice I get something completely different.
Example
Previous transaction:
084fb53458bda42cf906dc2608fe962667188849e51e1dc13cd291cc13c97290
Round one sha256 (with hex as input using anyhash.com):
9bbbb52bff2c553f84942188c87674c5b641b266baeb7ca216bebec8cd6a95bb
Round two sha256 (hex input also):
e5a3d32d306ef94968e0f77e6b0b496bfe9d5cd0fe6246a4ba7fd2fddf11cdf1
This final value does not match the one given by coinb.in's transaction. Am I missing something here? I see that the other question mentions the transaction in reverse order, what exactly does this mean?

user74111: I've figured it out.
So in this case (and if you look up a previous transaction on sites like blockchain.info) the transaction ID is already the double-hashed transaction. The input to the new transaction is just the reverse of the transaction ID.
So my previous transaction starts:
90 72 c9 13 ...
and the full transaction created by coinb.in ends in:
... 13 c9 72 90

74111: <p>I'm having trouble performing the double-sha256 hash of the previous transaction, Step 3 in <a href="https://bitcoin.stackexchange.com/a/32695/74111">this explanation.</a></p>

<p>The previous transaction is: </p>

<p><code>084fb53458bda42cf906dc2608fe962667188849e51e1dc13cd291cc13c97290</code></p>

<p>I've input the full transaction I want to perform into coinb.in <a href="https://imgur.com/CwKM7UL" rel="nofollow noreferrer">as shown here</a>, giving me a full transaction of:</p>

<p><code>01000000019072c913cc91d23cc11d1ee5498818672696fe0826dc06f92ca4bd5834b54f08010000001976a91460077bce1849cc2a41e2ccaa6ec575b3f5b70a9d88acffffffff0120a107000000000017a9144574085e1ef5432a6b09218f3b6ab6128f8eb2a58700000000</code></p>

<p>From what I understand, the double-sha256 of the previous tx here is:</p>

<p><code>9072c913cc91d23cc11d1ee5498818672696fe0826dc06f92ca4bd5834b54f08</code></p>

<p>However when I perform sha256 twice I get something completely different.</p>

<p><strong>Example</strong></p>

<p>Previous transaction:</p>

<p><code>084fb53458bda42cf906dc2608fe962667188849e51e1dc13cd291cc13c97290</code></p>

<p>Round one sha256 (<a href="https://imgur.com/LB4syMF" rel="nofollow noreferrer">with hex as input using anyhash.com</a>):</p>

<p><code>9bbbb52bff2c553f84942188c87674c5b641b266baeb7ca216bebec8cd6a95bb</code></p>

<p>Round two sha256 (hex input also):</p>

<p><code>e5a3d32d306ef94968e0f77e6b0b496bfe9d5cd0fe6246a4ba7fd2fddf11cdf1</code></p>

<p>This final value does not match the one given by coinb.in's transaction. Am I missing something here? I see that the other question mentions the transaction in <a href="https://bitcoin.stackexchange.com/questions/32628/redeeming-a-raw-transaction-step-by-step-example-required?newreg=c5b80dbb751b4ece9eca8587766fd459">reverse order</a>, what exactly does this mean?</p>
 74111: <p>I've figured it out.</p>

<p>So in this case (and if you look up a previous transaction on sites like blockchain.info) the transaction ID is already the double-hashed transaction. The input to the new transaction is just the reverse of the transaction ID.</p>

<p>So my previous transaction starts:
<code>90 72 c9 13 ...</code></p>

<p>and the full transaction created by coinb.in ends in:
<code>... 13 c9 72 90</code></p>
