<p>If the first output is in the mempool, you can use it in a subsequent transaction without the node throwing an error. However, there is no assurance that both transactions will be part of the same block.</p>

CC BY-SA 4.0
2022-07-02T02:42:26.477Z
When would be such case that both the transactions wouldn't be included in the same block? For example under heavy blockchain load?
et97
CC BY-SA 4.0
2022-07-02T06:47:42.837Z
I'm not sure of the exact scenario, I believe it works like first come first serve basis, so    all trxs in mempool may not fit in one block
Prashanth S.
CC BY-SA 4.0
2022-07-02T02:22:23.790Z
2022-07-02T02:22:23.790Z
Prashanth S.
<p>Let's say I lock some ADA at a script address. Someone who knows the redeemer value can unlock this ADA. Is it possible to include a redeeming tx in the same block as the tx which locks the ADA at the script address? Provided that the script tx was first in the mempool? Or is it necessary to wait at least for 1 confirmation before the ADA can be unlocked from the script address?</p>

<script-addresses><redeemer>
Is it possible to consume a script UTxO in the same block?
# Is it possible to consume a script UTxO in the same block?

(Asked by: username_0 on 2022-07-02)

Let's say I lock some ADA at a script address. Someone who knows the redeemer value can unlock this ADA. Is it possible to include a redeeming tx in the same block as the tx which locks the ADA at the script address? Provided that the script tx was first in the mempool? Or is it necessary to wait at least for 1 confirmation before the ADA can be unlocked from the script address?

**Tags:** script-addresses, redeemer

---

## 1 answers

### Answer by username_1 on 2022-07-02. Score: 2

If the first output is in the mempool, you can use it in a subsequent transaction without the node throwing an error. However, there is no assurance that both transactions will be part of the same block.

> **Comments:**
> **username_0**: When would be such case that both the transactions wouldn't be included in the same block? For example under heavy blockchain load?  
> **username_1**: I'm not sure of the exact scenario, I believe it works like first come first serve basis, so    all trxs in mempool may not fit in one block  

---

