what about the other input (the confirmed UTXO used on the transaction, address ends in avh5). Can it be spent on a different transaction?
I saw that you've already did that which replaced the mentioned "screwed_TXID" in the OP, it's now confirmed.Not only that, this screwed_TXID has now some descendants because the change address of screw_TXID was used for another transaction (for some reason, the wallet of this entity thought it was a good idea instead of using available UTXO's to forge that transaction)
Since you did replaced it, those descendant transactions are now dropped from mempools.If you do not want the client to spend unconfirmed UTXO in your next transactions (in Electrum as hinted in the OP),
Tick the setting "Spend only confirmed coins" in the settings icon [
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fwww.talkimg.com%2Fimages%2F2024%2F04%2F25%2FrUBEz.png&t=663&c=xWV_aGO53x5Uvw)
I managed to spend the confirmed UTXO (ending on avh5) that was part of the screwed_transaction. How? Well, on Electrum the status was "Unconfirmed parent" but for some reason it suddenly changed to "Local", so I click "remove" and it "reverted the broadcast of the screwed_TXID" and I could select the confirmed input (avh5) to use it on a different transaction. Now, I went back to Wallet A where the unconfirmed UTXO (ending on 86t) part of screwed_TXID originated, the thing is I can't manage to do the same (convert an "unconfirmed parent" transaction to "Local" to spend only the confirmed inputs). If i dont do this, I cant spend the confirmed inputs. What to do now? How do I convert an "unconfirmed parent" transaction" to Local? I think it has to do with the server I'm connected to, I tried to change it but I couldn't get the same result