3249a63 Fix logging - CTransaction::ToString() always has `\n` at the end of a string, avoid adding empty line
ec03753 make mnw errors and ThreadCheckDarkSendPool less spammy
5b678af fix errorMessage - it should not have `\n`, let output code handle line endings instead
a81cdf7 rename `dash-darksend` thread to `dash-privatesend`
5e4f468 fix/remove outdated code
f1c9678 Break tooltip about third party urls in 2 lines

…oin#838) (bitcoin#893)

There is no need to append all the addresses for each output
to the transaction destination address which is displayed in the ui.
This is because each output for a multi-output transaction is already
displayed as an individual transactions.  Furthermore, concatenating
all the output addresses only make it impossible to know for which
output this transaction is for without spending the time to open
the transaction details and search through the list of outputs to
find the one associated with this amount; and again if two outputs
had the same amount you would not be able to make the differentiation.

This commit reverts to the previous correct behavior when displaying
mulit-output transactions.