<p><code>getContinuingOutputs</code> makes use of <code>findOwnInput</code> to find all outputs at the script address.</p>
<p><a href="https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/src/Plutus.V1.Ledger.Contexts.html#findOwnInput" rel="nofollow noreferrer"><code>findOwnInputs</code></a> only returns <code>Maybe TxInInfo</code>.</p>
<p>See here fore implementation details:
<a href="https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/src/Plutus.V1.Ledger.Contexts.html#getContinuingOutputs" rel="nofollow noreferrer"><code>getContinuingOutputs</code></a></p>

CC BY-SA 4.0
2022-06-13T12:28:37.147Z
2022-06-13T12:28:37.147Z
Will
<ul>
<li>findOwnInput get the actual utxo being consumed and validated for that validator in that moment.</li>
<li>same validator could run more than one time if you are consuming more than one utxo at the smart contract address. Every time findOwnInput will give you different result.</li>
<li>getContinuingOutputs will give you all the utxo at the outputs that are going to be locked and saved in the contract address after the transaction.</li>
</ul>
<p>Example:</p>
<p>I create a transaction using Utxo1 and Utxo2 as inputs and with two expected outputs, one utxo3 going again to the contract and another going to some wallet, utxo4</p>
<p>The transaction will execute the contract two times for validate the consume of utxo1 and utxo2.</p>
<p>In the first run of the validator, findOwnInput  will give you Utxo1
In the second run will give you Utxo2</p>
<p>In all the runs  getContinuingOutputs  will give you the output going to the contract, in this case Utxo3</p>

CC BY-SA 4.0
2023-03-17T16:05:44.723Z
2023-03-17T16:05:44.723Z
Manu Padilla
<p>Applying the functions (1) findOwnInput and (2) getContinuingOutputs in a context both return TxOut. What is the difference between these two TxOut?</p>

<plutus><context>
What's the difference between these two TxOut?
# What's the difference between these two TxOut?

(Asked by: username_0 on 2022-06-13)

Applying the functions (1) findOwnInput and (2) getContinuingOutputs in a context both return TxOut. What is the difference between these two TxOut?

**Tags:** plutus, context

---

## 2 answers

### Answer by username_1 on 2022-06-13. Score: 1

`getContinuingOutputs` makes use of `findOwnInput` to find all outputs at the script address.

[`findOwnInputs`](https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/src/Plutus.V1.Ledger.Contexts.html#findOwnInput) only returns `Maybe TxInInfo`.

See here fore implementation details:
[`getContinuingOutputs`](https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/src/Plutus.V1.Ledger.Contexts.html#getContinuingOutputs)


---

### Answer by username_2 on 2023-03-17. Score: 0

* findOwnInput get the actual utxo being consumed and validated for that validator in that moment.
* same validator could run more than one time if you are consuming more than one utxo at the smart contract address. Every time findOwnInput will give you different result.
* getContinuingOutputs will give you all the utxo at the outputs that are going to be locked and saved in the contract address after the transaction.

Example:

I create a transaction using Utxo1 and Utxo2 as inputs and with two expected outputs, one utxo3 going again to the contract and another going to some wallet, utxo4

The transaction will execute the contract two times for validate the consume of utxo1 and utxo2.

In the first run of the validator, findOwnInput will give you Utxo1
In the second run will give you Utxo2

In all the runs getContinuingOutputs will give you the output going to the contract, in this case Utxo3


---

