If the transaction has been broadcast then resetting multibit isn't going to help it get confirmations. What you want to do if you're worried about it getting confirmed sooner is to send out a competing transaction with more fees. To do that, I'd just import that privkey into some other wallet that doesn't know about the unconfirmed transaction and send again with a higher fee.
Thanks for the reply. This is the first time I have had a transaction not confirm. I am trying to learn the causes and the fix now in a hurry as it is a fairly large transaction. At least to me it is.
So sometimes transactions don't happen fast because the fee is set to low?
Can I export wallet out of multibit and into Bitcoin core wallet and then try and do what you suggest?
If I wait a couple of days will multibit stop broadcasting and just cancel the transaction so I can retry?
This transaction has been seen by 16 peers but still no confirmations.
I honestly can't remember how long multibit will keep rebroadcasting that transaction if it's never included. I assume that at some point you must be right. I also imaging that the answer is somewhere upthread if you search carefully. With respect to causes, yes, transactions compete for inclusion in blocks and including a higher fee will provide a higher likelihood of sooner inclusion. Up until recently, though, even no-fee transaction were usually eventually included. And yes, If I was you and I was trying to get a quick confirmation on this, I'd look at (a) whether you included a fee and whether it was high enough, depending on the answer to (a), do (b) resend a competing transaction with a higher fee, or just wait (maybe you included a good fee but are just unlucky, it can happen).
