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
Search
• When visiting hashscan, and typing in an EVM address (which has not yet been activated on Hedera) in the search bar, it doesn't display anything and won't let me click search to view that EVM address as an "unactivated account" with a message that tells me to send HBAR or tokens to the account to activate it.
Search
• Allow for someone to search for an EVM address in the search bar that is not currently active — ideally, instead of the "account" tag that appears in the search results, a tag that says "Inactive Account" appears and displays the EVM address below it.
Problem
Two parts to this issue:
Search
• When visiting hashscan, and typing in an EVM address (which has not yet been activated on Hedera) in the search bar, it doesn't display anything and won't let me click search to view that EVM address as an "unactivated account" with a message that tells me to send HBAR or tokens to the account to activate it.
Account Page for Inactive EVM Address
• Upon manually entering an inactive EVM address in the URL bar manually (i.e. https://hashscan.io/mainnet/account/0xABa701270045F0269603cC4850242AFEeFc65F63?pc=1) — the EVM address is not displayed in the "EVM Address" field at the top (screenshot).
Solution
Search
• Allow for someone to search for an EVM address in the search bar that is not currently active — ideally, instead of the "account" tag that appears in the search results, a tag that says "Inactive Account" appears and displays the EVM address below it.
Account Page for Inactive EVM Address
• In the EVM Address field (i.e. the EVM address field at the top of this page: i.e. https://hashscan.io/mainnet/account/0xABa701270045F0269603cC4850242AFEeFc65F63?pc=1) — have the field be filled in with the EVM address and make it "copyable".
Alternatives
None
The text was updated successfully, but these errors were encountered: