Just like others have said, you’re trying to spend a transaction using same client as the one that broadcasted the first transaction which is yet to get confirmed and since the node already has it then it is a conflict transaction and is seeing as a double spending which could get it dropped.
What you will do is to broadcast a new transaction from a different wallet so that it will be broadcasted by a node different from the first transaction. You can also broadcast the transaction from
https://blockchair.com/broadcast if you have raw transaction HEX.
Or better still import the seed phrase into BlueWallet and try to get the old transaction RBFed or if you have the first transaction receiving address then import that wallet seed into wallet that supports CPFP and increase the transaction fee of the first transaction
I tried 'BlueWallet' bump fee but error masses.
it is my final balance now but the old balance has been instilled in my wallet, I tried 0.00095895 BTC to send this amount but the same error.
Trust wallet doesn't support coin control so manually sending certain amount of BTC wont cause it to spend a specific UTXO.
Since it shows the total amount from those two UTXOs, then your wallet must be missing your old transaction (
as seen in the history) but their node's mempool still has it.
My suggestion above is to find a way to sync your transaction history to the blockchain so that your old transaction will show
and at the same time, its input wont be used in your new transaction.
And based from my test, they only have that scroll-down feature to refresh the wallet, try to find if there's any other way to rescan for transactions.
Thanks, @nc50lc tried 'BlueWallet' import phrase but not solved, so wait and see.
