I. Product Development
1.Completed page loading speed optimization
For better user experience, TRONSCAN has completed its optimization of the page loading speed, shortening the opening time of the site by 20%.
2.Developed real-time calculation scheme for obtaining energy/bandwidth by freezing TRX
To provide convenience for users to gain information about the energy/bandwidth as they are obtaining them by freezing TRX, we have developed a real-time calculation scheme, which will be launched and available after being tested.
3.Visual redesign
To improve the UI aesthetics and usability of TRONSCAN, our website is being redesigned overall. Please stay tuned.
4.CSV download upgrade
CSV download support will be added in the following pages for easier access to transaction information
Account > transfers, transactions, internal transactions
Token > token transfers
Contract> transactions, internal transactions
II. Operation Update
1.Further cooperation with DappReview
For users to better understand the TRON blockchain, TRONSCAN has worked with DappReview to add portals to each other’s website, which will streamline the operation process and improve the efficiency for users to search information.
2.Three new articles for TRONSCAN CLASS
Three articles themed Token Issuance, TRC10 & TRC20 Comparison and TRC10 Transfer in Smart Contracts respectively are published to help users better understand tokens on the TRON blockchain.
3. Key issues for this week: Why is my transfer not showing any result & why can I only see internal contract transactions in the last two weeks
Why is my transfer not showing any result: currently, TRONSCAN cannot show transfer results for TRC10 tokens. However, transactions that are in the “confirmed” status on TRONSCAN are considered successful. We will add the search feature for TRC10 token transfer results. Please stay tuned.
Why can I only see internal contract transactions in the last two weeks: since the search feature for internal contract transactions is only added two weeks ago, it is only able to search transactions that happened after the feature was launched.
