Author

Topic: how to differentiate which address is getting paid within Litecoin Wallet? (Read 464 times)

newbie
Activity: 55
Merit: 0
On this one rig I currently have THREE separate Litecoin wallet addresses within the single Litecoin wallet app. Basically one per pool that I'm currently testing. Easy enough to setup and track "TOTAL" transacations and total LTC's paid out to my wallet....BUT on the transactions page I'm UNABLE to separate or differentiate between the three addy's...

I can see it's "supposed" to be possible and should be rather straight forward..

4 columns that are "Date", "Type", "Address" and "Amount"

There are drop downs for filtering the time frames or how you got them..mined, received, bought, other, etc...

Then the "Adress" column and this is where I should be able to do what I want.. and right about it there IS A BOX TO SEARCH BY ADDRESS OR LABEL... simple enough.. just pop in the specific wallet addy I want and...bingo! right? nope.. because.. EVERY transaction only has the little "miner twin pic's" symbol with "(n/a) next to it.. so it's as if they are all mixed in together..

This is where it "should" have had ONE of the THREE different LTC Wallet ADDY's I have setup for EACH transaction..making it easy to see, filter and search...but doesn't! WHY?

Anyone know? Any way to change a setting or something to do so.. or another way to search..I know online at "explorer.litecoin.net" there is specific breakdowns with info about each trans to each addy and what block it came from and amount and all that.. it's ok..for now..and I'm forced to search this way...but preferrably, I'd like to do so  within the wallet..  it should be MUCH simpler and not sure why this easy app that is setup to do so, is not doing so.

Thanks!


*edit/update* I noticed within the setting of the client on the last tab (display) there is a checkbox for "Display addresses in transaction list" which is EXACTLY what I want and what it should be.. it's checked but still just n/a in list... does this mean the client itself has bug?

Jump to: