My suggestion is to add a column that has a value of "value at time of transaction", this would be extremely useful for, for instance, dealing with taxes when you have a ton of transactions. The value could be fetched from blockchain.info for instance, im not sure about their API but I have been using that site to manually check the value of BTC in fiat at the time a particular transaction happened. I don't know any software or website that does this so manually put it inside an .csv which is annoying. Would be cool if you could dump an export .csv from Core's client into your software and get this column neatly displayed.
I've added "price history" feature that will add
a new field to each transaction based on its confirmation time that includes the USD value of that transaction at that time. It will use CoinDesk API since it is more common as an average price source.
The problem is that I'm not sure how to display this feature. For now you can only update this through the ForkBalance window and there is no displaying option but you could use your wallet.json file to analyze if you wanted. I'll probably do some major changes in this app as soon as I get some more free time, making things more automated and update everything in one place and skip repetition (since some parts are updated multiple times even if you already have the history).
Do you have any suggestions for displaying it? I was thinking a line chart showing the history.
As for bitcoin-core compatibility I have it in my TODO list but it is at the bottom of it.
Unfortunately im not familiar with the CoinDesk API. Im really looking forward to "fiat price at the time" information. A graph per each tx would be nice, but maybe a bit overkill for now. Just a simple column next to the txid that shows the value at the time of said tx would be incredibly useful for, like I said, filling taxes.
I would make txid's clickable and an explorer of choice would be opened because sometimes you want to check something and you like the layout of a certain explorer but this just comes to personal preference in how to design the program.
If importing the csv is not near, then it may be a bit of a PITA for those that have tons of transactions, one would need to import each tx one by one and in chronological order but I guess it's better than nothing for now, since all I have right now is manually checking each tx on an explorer id which is hell (btw im talking about having the entire tx history imported in your program with all the data, not just current watch only addresses with funds, so you would have a window for watch only current funds and another window where you can import your entire wallet.dat tx history so you can check those things without having to fire the resource consuming full client in your airgapped computer or wherever you store tx history)
