Transaction view should display a calculated net 'action' instead of multiple spend and output actions

[turbocrime]

Is your feature request related to a problem? Please describe.

Transactions contain (possibly multiple) spend actions that are always larger than the requested spend amount, and an extra output action returning 'change' to achieve balance.

But, the user does not care that a transaction involved multiple inputs and balancing outputs. This is an implementation detail.

Describe the solution you'd like

The user cares about the effective net per account involved in the transaction.

Transaction views could group spend and output actions by asset, then source and destination address. Then, the view could display a single effective net amount for each asset and address, or possibly between address pairs.

Grouping spends and outputs into fewer items would make transaction views more compact and easier to understand.

Additional context

A collapsed group should be expandable to view details.

Raw JSON is available to users interested in complete data.

The net activity of single assets or between address pairs may not be meaningful information for all transactions.

Other components could take advantage of the same calculation code when displaying transactions in a table.

[TalDerei]

reference #2000

[hdevalence]

Yes, this should be tracked by the existing transaction summary tracking issue, closing as duplicate