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
the transaction status view contains includes a fixed text "TX"
they are some transactions that do not include any icon (check or x) to indicate the status
Based on the discussion in the explorer team channel in discord:
For mining transactions, the amount will be always 0, thus status cannot be provided for them
For 'transfer transactions', the 'moneyFlew' field determines the status (check for true and x for false) because it indicates if the funds were actually transferred or not
Some possible options for improving the UI here:
a) to remove the "TX" text because if we keep it fixed, doesn't bring any added value. i.e how web wallet has this
b) to use different strings or icons to identify the 'type of transaction' instead of having the fixed TX.
An idea/proposal that came out in the discussion:
"if it's a mining transaction display the icon of a pickaxe
if it's a transfer, display a dollar
successful transfers are green dollars, failed ones are red dollars"
@Orestasas could you please have a look on this and advise if there is room for improvements here?
The text was updated successfully, but these errors were encountered:
As it can be seen in the image below (taken from https://betaexplorer.qubic.org/network/tick/15708701):
Based on the discussion in the explorer team channel in discord:
Some possible options for improving the UI here:
a) to remove the "TX" text because if we keep it fixed, doesn't bring any added value. i.e how web wallet has this
b) to use different strings or icons to identify the 'type of transaction' instead of having the fixed TX.
An idea/proposal that came out in the discussion:
"if it's a mining transaction display the icon of a pickaxe
if it's a transfer, display a dollar
successful transfers are green dollars, failed ones are red dollars"
@Orestasas could you please have a look on this and advise if there is room for improvements here?
The text was updated successfully, but these errors were encountered: