explorer
explorer copied to clipboard
Wrong account balance for multisig cosignatories accounts
I have picked out two random multisig accounts. If a Multisig co-signer account is clicked before the explorer is loaded properly, then often an incorrect amount is displayed for the Multisig co-signer account. The amount of the multisig account is displayed and not the amount of the multisig co-signer account.
- Enter the Multisig account address in the search field (or go back with the arrow button of the browser).
- Click on the address of the Multisig cosignatory account before the page is loaded correctly.
-
Multisig account:
NA4BJ5-V4L67Q-EF4537-LKAAFQ-LK6GCS-R6VVDQ-CTY = 3,010,353.765133 XYM -
Mulitsig cosignatories: NBONDH-ZK45S6-HGXO7S-3G3VM6-BMZTXX-6HLZOR-TKA = 1,137.591510 XYM
-
Multisig account: NCV677-4QIZJA-U75AKG-DC5LJK-EQLZZY-OFVHEY-ABQ = 3,023,800.700608 XYM
-
Multisig cosignatories: NBABRK-FNIMO2-IL4CCB-7IYICU-3GVHOC-WBPXNS-PJI = 50.000000 XYM NB3LYY-GES7TZ-OGDJ7X-OYN2NB-7YFMP5-ISU777-ZIA = 239.565960 XYM
I believe it should cause by some cache issue on the browser. I will do some investigation on this.
Hi, I tried it with different browsers, all of which had different delays in loading time, gave the same result. The Multisig cosig address is one of the first addresses displayed when an explorer loads slowly. This of course tempts to go further and shorten the loading time. Thus one receives a wrong display in the explorer. Thx
video: https://share.getcloudapp.com/5zuYE8no
Thanks for the video. Yes, sometimes it happens that the display changes and shows the correct amount. Unfortunately, this is not always the case. Sometimes the display did not change with the wrong amount.
I had debug on this issue.
- When request Account A (pending account info update in vue state).
- We click on back button on explorer, it made request on Account B (pending account info update in vue state).
- The state info update to Account A (response come back).
- The state info update to Account B (response come back).
I havent found a solid solution yet, but will disucss with team.