Force closing a Lightning Channel due to unclear transaction

I figured it out. Just go ahead and remove this thread.

This proves that your transaction from force closing the channel is successful since the TX is already confirmed and funds credited back to your address so the pending incoming TX is something that is unrelated to your lightning network force closing (correct me if I am wrong). The pending TX broadcasted with 1sat/vbyte which is too low when we look at the current mempool status: https://mempool.space/ So most nodes didn't pick your TX and eventually, it will be dropped from the mempool after 14 days if it's not rebroadcasted again.

Your topic does not need to be deleted if you’ve found solution to the question you are asking about. This place is more like a school that will learn, your question that was answered can easily be searched by any user to find a solution to a similar problem in the future. I see no need you’re requesting for your topic to be deleted.

What a selfish move to ask for the deletion of your topic once your issue is resolved or a solution emerged. You found a solution? That's nice. You keep the solution to yourself? Not so nice. Do you understand the purpose of this forum? One purpose is to share knowledge. You may not be the only one who had such a problem that made you post here. Why not share the solution so others can benefit from it? If anyone needs to read the initial post which the OP has deleted, it can be found here: https://ninjastic.space/post/62845607

Thanks for the link. If we put the pieces of information together, OP's solution was to remove or "abandon" that local transaction from his history. That freed the other input which has the significant amount ($300+); which he spent 16 days ago, right after posting this thread. The other input (330sat) which was the output of his force-close transaction was consolidated 5 days ago. He thought it's related because that dropped transaction included this as input.