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
As of now, when you search for an address, it showcases you the total amount of livecells for this address and the amount of UDTs, but its not showcasing how many cells are used by which UDT and with what capacity.
Would it be possible to add a feature to the explorer, showcasing the livecells per address/account per udt with the capacity displayed without hovering over the specific cell?
So basically, instead of redirecting to the contract cell when you click on cketh for example (or maybe a additional button), i envision a page which showcases the livecells + capacity and of course the token amount in the cell for a specific address.
Regards
The text was updated successfully, but these errors were encountered:
So, i can see the livecells, but dont know how many cells get occupied by what specific sUDT, their amount and the capacity. Basically yeah, what you suggested.
So, i can see the livecells, but dont know how many cells get occupied by what specific sUDT, their amount and the capacity. Basically yeah, what you suggested.
Thank you for your suggestion, we will consider this feature.
As of now, when you search for an address, it showcases you the total amount of livecells for this address and the amount of UDTs, but its not showcasing how many cells are used by which UDT and with what capacity.
Would it be possible to add a feature to the explorer, showcasing the livecells per address/account per udt with the capacity displayed without hovering over the specific cell?
So basically, instead of redirecting to the contract cell when you click on cketh for example (or maybe a additional button), i envision a page which showcases the livecells + capacity and of course the token amount in the cell for a specific address.
Regards
The text was updated successfully, but these errors were encountered: