AML check on NEAR

NEAR accounts can be readable names like alice.near or 64-character hex strings, so always check the exact account ID, not how familiar the name looks.

Address formatNamed accounts like alice.near, or 64-character hex implicit accounts (0x… accounts also exist)ab6487365b0f5b202995f81524fe5194c55a6cf978874bbeb5d1d9796f87c5e7Example for illustration, not a real address.
Note

On NEAR, a name like alice.near is only an account ID and does not prove who owns it. Subaccounts such as app.alice.near are separate accounts that the parent account cannot control.

Services that check NEAR

01EllipticEnterprise platformPrice on requestSupportedNot scored
02Crystal IntelligenceEnterprise platformPrice on requestSupportedNot scored
03TRM LabsEnterprise platformPrice on requestSupportedNot scored
04Quppy AML BotUse with careTelegram bot5 USDT for 11 checks, down to 0.23 USDT a checkSupported7.5
05Merkle ScienceEnterprise platformPrice on requestNot verifiedNot scored

How to check a NEAR address

  1. Get the public addressAsk your counterparty for the address they will send from — or copy it from the incoming transaction.
  2. Pick a service that covers NEARChoose one marked “Supported” in the list above. Paste the full account ID exactly as written (named, 64-character hex, 0x or 0s) and confirm the checker supports that format; a lookalike name is a completely different account.
  3. Run the check and read itIf funds arrived through a cross-chain swap service such as NEAR Intents, they may have started on another blockchain, so a NEAR-only check may not show their full history.
A real AML check needs only a public address. Never share a seed phrase or private key.

NEAR specifics

  • NEAR addresses come in several forms: readable named accounts like alice.near, 64-character implicit accounts tied to a key pair, Ethereum-like 0x accounts, and newer deterministic accounts starting with 0s.[1]
  • A NEAR account can hold several keys at once: full-access keys control everything, while function-call keys can only call one named contract and cannot attach NEAR tokens to the call.[2]
  • Because keys can be added or removed, whoever controls a NEAR account can change over time, and an account with all keys removed becomes locked so no one can transact from it.[3]
  • Accounts that store data on NEAR must lock part of their balance for storage, at 1 NEAR per 100 kb, so an account's spendable balance can be lower than its total balance.[4]
  • NEAR Intents is a multichain transaction protocol where users state an outcome (such as swapping one token for another), off-chain market makers compete to fill it, and a Verifier smart contract on NEAR settles the result.[5]

Common risks on NEAR

FAQ

Does a name like alice.near prove who owns the account?

No. A named account is just an account ID, similar to a web domain. Subaccounts such as app.alice.near are separate accounts, and the parent account has no control over them.

What is a 64-character hex address on NEAR?

It is an implicit account: an address made from a public key, so it belongs to one specific key pair rather than a chosen name.

How do I check a NEAR address for AML risk?

Copy the public address, open one of the services listed above that supports NEAR, and run the check. You never need a seed phrase or private key.

What does “Not verified” mean?

The service claims support somewhere — in marketing copy or a third-party page — but its own docs, pricing or FAQ do not list the network. Treat it as unknown.

Sources

  1. NEAR Docs (docs.near.org) — Address (Account ID). Checked 4 Oct 2026.
  2. NEAR Docs (docs.near.org) — Access Keys. Checked 4 Oct 2026.
  3. NEAR Docs (docs.near.org) — Access Keys. Checked 4 Oct 2026.
  4. NEAR Docs (docs.near.org) — Storage Staking. Checked 4 Oct 2026.
  5. NEAR Docs (docs.near.org) — NEAR Intents. Checked 4 Oct 2026.