Quote from: HCP on August 27, 2017, 01:27:17 AM

Can you provide the TransactionID? I'd like to check to see if your transaction has actually propagated properly...

It's quite possible you could just "import" your private keys rather than "sweeping" them... which would get around the mempool conflict error, but if the transaction still exists (it's quite possible that MBC is rebroadcasting your transaction) then you still wouldn't be able to send a new transaction anyway...

https://www.blocktrail.com/BTC/tx/0e9a9d0861a90e29427c7810801effab2869bbce9dd5df5b155b5084565251ee
https://blockchain.info/tx/0e9a9d0861a90e29427c7810801effab2869bbce9dd5df5b155b5084565251ee

That's why I didn't do the import.

I went through Multibit support and tons of threads, but double spend didn't work at all.

(transaction details on blockchain of the above transaction are the same as the earlier - 0e9a9d0861a90e29427c7810801effab2869bbce9dd5df5b155b5084565251ee sent on 22nd)