<p>If you have a UTxO output A, and you submit a transaction that spends UTxO A, everything should be fine. If you submit a second transaction that also spends UTxO A, then the transaction should fail because the UTxO you are trying to spend has already been spent. This is how the UTxO accounting model works.</p>
<p>Also, I am rather unsure what you mean by</p>
<blockquote>
<p>I believe this is due to the UTxO not being updated,</p>
</blockquote>
<p>In the UTxO accounting model, UTxOs are <em>never</em> updated.</p>
<p>I suggest you read up on the differences between the account based model used in Ehtereum and the UTxO accounting model used in Cardano (and Bitcoin).</p>

CC BY-SA 4.0
2022-09-29T03:11:48.153Z
Thanks for the answer! As for the difference between UTxO and the account model you pointed out, I thought I understood it, but my explanation was incorrect in this question. UTxO is consumed and new UTxO is generated. I had represented this as an update. And you are trying to use the same Input for the first transaction and the second transaction, right? As for the language, I am Japanese and use machine translation for English, so forgive me if there are some oddities!
yousuke
CC BY-SA 4.0
2022-09-29T05:42:09.380Z
Yes, if a transaction consumes a UTxO, any subsequent transactions that try to consume the same UTxO will fail because the UTxO has already been spent and no longer exists in the UTxO set. Reading you original post, I would not have guessed that you were using machine translation.
Erik de Castro Lopo
CC BY-SA 4.0
2022-09-29T02:56:05.817Z
2022-09-29T02:56:05.817Z
Erik de Castro Lopo
<p>Sending consecutive transactions will result in an error.
Using the simple-transaction example below, a transaction is created in Cardano-Serialization-Lib and sent to the blockchain using BrokFrost.<br />
<a href="https://github.com/blockfrost/blockfrost-js/tree/master/examples/simple-transaction" rel="nofollow noreferrer">https://github.com/blockfrost/blockfrost-js/tree/master/examples/simple-transaction</a></p>
<p>At this time, after one transaction is sent. If I create and send transactions consecutively without waiting for a time, I may get the following error and not be able to send.</p>
<pre><code>Transaction db6388f73ed195c30ea264dc968ea364d16fa7a097ddae0236d9fbf1fa150df8 rejected&quot;transaction submit error ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (UtxoFailure (FromAlonzoUtxoFail (ValueNotConservedUTxO (Value 0 (fromList [])) (Value 206069713 (fromList []))))),UtxowFailure (UtxoFailure (FromAlonzoUtxoFail (BadInputsUTxO (fromList [TxIn (TxId {_unTxId = SafeHash \&quot;607d1531d04bb56da9a6145c784ae2c1b59980ca3703b78777404516d41e93b5\&quot;}) (TxIx 1)]))))])&quot;
</code></pre>
<p>I believe this is due to  trying to use the same Input for the first transaction and the second transaction , is there any way to resolve this?
Also, in this example, what condition is specified in the UTxO of the transaction's Input?<br />
What I would like to achieve</p>
<ul>
<li>We want to create and send a transaction without time after sending once.
Example Send 100 transactions per minute from one address.</li>
</ul>
<p>What we want to know</p>
<ul>
<li>If there is another way to specify the UTxO of Input, is it possible to create and send transactions continuously by changing it?</li>
</ul>

<transaction><cardano-serialization-lib><utxo><blockfrost>
Sending consecutive transactions will result in an error
# Sending consecutive transactions will result in an error

(Asked by: username_0 on 2022-09-29)

Sending consecutive transactions will result in an error.
Using the simple-transaction example below, a transaction is created in Cardano-Serialization-Lib and sent to the blockchain using BrokFrost.
https://github.com/blockfrost/blockfrost-js/tree/master/examples/simple-transaction
At this time, after one transaction is sent. If I create and send transactions consecutively without waiting for a time, I may get the following error and not be able to send.
Transaction db6388f73ed195c30ea264dc968ea364d16fa7a097ddae0236d9fbf1fa150df8 rejected"transaction submit error ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (UtxoFailure (FromAlonzoUtxoFail (ValueNotConservedUTxO (Value 0 (fromList [])) (Value 206069713 (fromList []))))),UtxowFailure (UtxoFailure (FromAlonzoUtxoFail (BadInputsUTxO (fromList [TxIn (TxId {_unTxId = SafeHash \"607d1531d04bb56da9a6145c784ae2c1b59980ca3703b78777404516d41e93b5\"}) (TxIx 1)]))))])"

I believe this is due to  trying to use the same Input for the first transaction and the second transaction , is there any way to resolve this?
Also, in this example, what condition is specified in the UTxO of the transaction's Input?
What I would like to achieve

We want to create and send a transaction without time after sending once.
Example Send 100 transactions per minute from one address.

What we want to know

If there is another way to specify the UTxO of Input, is it possible to create and send transactions continuously by changing it?

**Tags:** transaction, cardano-serialization-lib, utxo, blockfrost

---

## 1 answers

### Answer by username_1 on 2022-09-29. Score: 1

If you have a UTxO output A, and you submit a transaction that spends UTxO A, everything should be fine. If you submit a second transaction that also spends UTxO A, then the transaction should fail because the UTxO you are trying to spend has already been spent. This is how the UTxO accounting model works.

Also, I am rather unsure what you mean by

> I believe this is due to the UTxO not being updated,

In the UTxO accounting model, UTxOs are *never* updated.

I suggest you read up on the differences between the account based model used in Ehtereum and the UTxO accounting model used in Cardano (and Bitcoin).

> **Comments:**
> **username_0**: Thanks for the answer! As for the difference between UTxO and the account model you pointed out, I thought I understood it, but my explanation was incorrect in this question. UTxO is consumed and new UTxO is generated. I had represented this as an update. And you are trying to use the same Input for the first transaction and the second transaction, right? As for the language, I am Japanese and use machine translation for English, so forgive me if there are some oddities!  
> **username_1**: Yes, if a transaction consumes a UTxO, any subsequent transactions that try to consume the same UTxO will fail because the UTxO has already been spent and no longer exists in the UTxO set. Reading you original post, I would not have guessed that you were using machine translation.  

---

