You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice to also have the receiving address alongside the transaction ID in the CSV export. Optionally, also the destination address(es) for sends.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion, but how do you propose multiple addresses for one transaction are handled? Receiving is probably rarer, but when sending it's quite frequent (e.g coinjoins). Also, do you have a specific use case in mind?
My main use case is related to #1233 and having an easy way to lookup the trail of an UTXO. In some cases it would be helpful to also have the address available — so here it is more like an additional data point I could search for and then find the connected txID. In that sense I wouldn't even mind having them like labels in a single column, joined by comma or so.
It'd be nice to also have the receiving address alongside the transaction ID in the CSV export. Optionally, also the destination address(es) for sends.
The text was updated successfully, but these errors were encountered: