Quote from: coinHasher123 on December 16, 2017, 11:53:31 PM

Quote from: darkangel11 on December 16, 2017, 09:56:34 PM

Read this:
https://multibit.org/help/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html

There are two main reasons why a transaction gets stuck on "Seen by one peer" and does not propagate through the Bitcoin network. These are:
You lost your network connection and the transaction did not get sent successfully to the peer (did not broadcast)
The peer received the transaction but "did not like it" (did not relay)

There are various reasons why a peer does not relay a transaction. In a rough order of frequency they are:

There are lots of tiny inputs (under 5432 satoshis) in your wallet and the transaction fires the anti-spam rules.
The fee is too small and the peer chooses not to relay it.
The transaction is a double spend. Doubles spends aren't relayed through the network.

You can remove the transaction that never propagated by doing a 'Tools | Reset Block chain and Transactions'.

IMO this is where your problem lies. I'd reset and try again until it gets accepted. I see no other way since you can't upgrade to a newer version and can't increase the fee. Once you get the transaction to appear in the blockchain you can accelerate it, but without this happening there's not much you can do since it's still stuck in your wallet.

Thanks, I will try tonight

UPDATE:

From multibit client 5.14 tried to reset blockchain and transaction for 5 times, still show zero balance
Upgrade multibit to 5.19 and tries 2 more times still zero balance and the 3rd time the balance show up (0.1059325) but the last transaction no longer there (e08534c29b38b15221e5663250d779e5f548e2d4f636adf9dc32ec44254e9ea7)
So I think that transaction never got into the mempool and got dropped from the network

One thing I noticed the blockchain balance https://blockchain.info/address/158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N showing 0.10594026 and the multibit balance is 0.1059325 and the different is
0.00000776 in this transaction https://blockchain.info/tx/bdd2eb9ea6b74c9c0a2abacf019e3538497040296b6cf013430524111e29ad60 and has not confirm yet, why blockchain included the
0.00000776 if the tx still unconfirmed.

If I use multibit and send some btc to another address will the previous tx bdd2eb9ea6b74c9c0a2abacf019e3538497040296b6cf013430524111e29ad60 cause any problem.

Please helps

----------------------
UPDATE:

Problem solved,
I end up export private key from multibit and import in Bitcoin wallet and run command zapwalletes then rescan, balance show up correct, send another transaction out with higher fee and got confirm with 1 hour