user6982: 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?

user2094: 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.

6982: <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>
 2094: <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>
