Diagnose an account

Paste any Hedera account id or EVM address. Every read here is public — no wallet, no key, no .env.

Try:

Identity

Account id

0.0.2

EVM address

0x0000000000000000000000000000000000000002

Address form

evm-long-zero

Derived from the account NUMBER, not from a public key.

ECRECOVER compatible

ECRECOVER will NOT fail on this account — it will return a different, valid-looking address. Code that compares the two rejects a legitimate signature and cannot explain why. Verify through isAuthorized on the Account Service at 0x16a instead.

Key

Key type

ED25519

Verification route

is-authorized

ED25519 key. It has no EVM address of its own, so it cannot deploy contracts or sign EVM transactions. Verify through isAuthorized on 0x16a, and use an ECDSA account for anything EVM.

Usable with EVM tooling

Cannot deploy contracts or sign EVM transactions. The key type is fixed at account creation and cannot be changed.

Holding tokens

Automatic slots

0 free of 0

No automatic slots at all. A transfer of a new token to this account right now FAILS with TOKEN_NOT_ASSOCIATED_TO_ACCOUNT.

HBAR balance

33882216267.53675776 ℏ

mirror node· 5:43:46 AM

If you sent this account a new token: Airdrop

The recipient cannot be asked to sign — it is an account the sender does not control and cannot prompt. The kit sends an HIP-904 airdrop instead, where the SENDER pays the association fee and the recipient claims when ready.

Answered from the sender's side — you are looking at an account you do not control and cannot ask to sign. If it were your own wallet, the kit would have more options; that case is on /acquire.

Mechanism

HIP-904 TokenAirdropTransaction

Fee paid by

sender

Approvals from recipient

All four mechanisms, against this account

Hedera shipped three protocol changes at the association problem and produced four ways to solve it. Here is how each one fares for this specific account — including the ones that do not apply, and why.

Auto-slotHIP-23does not apply
The recipient has no free automatic slots and the sender cannot raise the limit on an account it does not control.
BatchHIP-551does not apply
Batching needs a signature from the recipient, and this account cannot be asked to sign.
Explicitdoes not apply
An explicit association must be signed by the recipient, and this account cannot be asked to sign.
AirdropHIP-904chosen
The sender pays for delivery or a pending airdrop. Creating the pending entry needs no recipient signature or HBAR; claiming it later requires recipient authorization and a funded payer. Token restrictions still apply.
fee paid by sender0 approvals from recipient