Quote from: knightdk on August 01, 2016, 02:12:32 PM

Quote from: TheD1ceMan on August 01, 2016, 02:07:43 PM

Quote from: knightdk on August 01, 2016, 02:03:40 PM

Quote from: TheD1ceMan on August 01, 2016, 01:59:25 PM

f6b1b353444789bfe9baa638f32fd7c6d37850d2818a59a7c419c133d0ac1d51: Seen by 1 peer. Pending/unconfirmed.
from 1CN5ea2C7whK2UYRjrSEvHSufKpFequdw / d9d8b5fd43c7c231c6f6143e4c1d556f4505a20be52cb2bfdad6ac9f51fad5d3:0
to 1BxnYyNsiejnsaxv7ddPGFYu16Hn7R6zfm 0.00299473 BTC
to 1CN5ea2C7whK2UYRjrSEvHSufKpFequdw 3.37690527 BTC

That isn't the actual raw transaction...

But, you can see that the second output there of 3.37690527 is your change output. I'm guessing that your wallet says you have 3.37690527 and you are trying to spend from it. However, that is the change output and it is tied up in this unconfirmed transaction.

it says in multibit that my balance is 3.37700529.
any idea what i need to do to fix this?

So I did a little bit of digging, and it looks like your transaction fee is too low. It is paying somewhere between 30 and 40 satoshis per byte, which, although not that low, isn't high enough to get you fast confirmations. When you sent it a month ago, the state of the network may have been different and may have required an even higher fee.

In order to fix this, you need to make your wallet forget that it made that transaction in the first place. I'm looking into how to do this. Which version of MultiBit are you using?

Should be multibit HD which should have a button "repair wallet" that should do it.

If Im wrong and its multibit classic "reset and rescan blockchain" (something along those lines) should do it.