Why can a transaction show zero?
Distinguish a rounded fiat amount, a zero-value contract action and a hidden spam transfer.
Oath Atmosphere · 1.0 (56)
Where to find it
History → transaction details
How to do it
- Compare the local-currency amount with the native quantity underneath it.
- If the local value rounds to zero but the native quantity is nonzero, the transfer can simply be too small to display at that currency’s normal precision.
- If the native amount is also zero, open the transaction and check its status, network fee and explorer record.
- For an outgoing native-coin entry, consider whether it records a contract call or another action that transfers no native coin but still has a network fee.
- If you do not recognize the activity, compare the complete sender, recipient and transaction ID. Do not rely on a short address fragment.
Zero-value incoming transfers and ordinary zero-value token-transfer entries are hidden by the history safety rules. Attackers can use such entries to put lookalike addresses into a wallet’s activity.
Oath can retain zero-value outgoing or self native-coin actions, and zero-value outgoing outcomes such as Failed, Canceled or Replaced. Hiding every zero would also hide meaningful actions.
A zero local-currency display, an unavailable quote and a zero native transfer are different situations. The detailed public transaction helps distinguish them.