AML check on Flow
Flow is a layer 1 blockchain with two address formats: short 16-character Cadence addresses and 40-character Flow EVM addresses (chain ID 747).
Check which of Flow's two address formats you were given before sending, and confirm that the receiving wallet or exchange supports that side of Flow.
Services that check Flow
How to check a Flow address
- Get the public addressAsk your counterparty for the address they will send from — or copy it from the incoming transaction.
- Pick a service that covers FlowChoose one marked “Supported” in the list above. A 0x address with 16 characters after the prefix is a Cadence account; one with 40 is Flow EVM. Do not assume a wallet or exchange accepts both.
- Run the check and read itNeither Tether nor Circle lists Flow for native USDT or USDC, so treat any stablecoin on Flow as a bridged token and check who stands behind it.
Flow specifics
- A Flow (Cadence) account address is 16 hex characters, usually written with a 0x prefix, and is assigned by the network in a fixed sequence rather than derived from a key.[1]
- Flow EVM mainnet uses chain ID 747 and FLOW as its currency, so Ethereum-style 0x addresses with 40 hex characters also exist on Flow.[2]
- Cadence-Owned Accounts (COAs) are EVM addresses controlled from a Cadence account; they begin with 0x000000000000000000000002 and exist only on Flow.[3]
- A Flow account can hold several keys with different weights, and keys can be added, removed or revoked by transaction, so control of an account can change while its address stays the same.[4]
- The Crescendo upgrade went live on Flow mainnet on 4 September 2024, adding full EVM equivalence alongside Cadence 1.0.[5]
- On 26-27 December 2025 an attacker exploited a bug in Flow's Cadence runtime (v1.8.8) to duplicate tokens; Flow Foundation puts the confirmed damage at about USD 3.9 million bridged off-network before the halt.[6]
- Flow Foundation says the roughly USD 3.9 million in bridged-out assets was laundered through THORChain and Chainflip, and 1,060 accounts were flagged as having received counterfeit tokens.[7]
- Validators halted the network about 6 hours after the first malicious transaction and Flow was restored on 29 December 2025 via an 'isolated recovery' plan instead of a rollback; the Foundation says no existing user balances were accessed.[8]
- Flow Foundation says 87.4 billion counterfeit FLOW were destroyed onchain by the Community Governance Council, completing the incident remediation.[9]
- Circle ended support for USDC on Flow (Cadence) on 3 September 2024, froze remaining balances and moved to manual redemption based on a snapshot.[10]
Common risks on Flow
FAQ
Why does Flow have two kinds of 0x address?
Flow runs its own Cadence environment (16-character addresses) and an Ethereum-compatible Flow EVM (40-character addresses, chain ID 747) on the same network.
Was Flow hacked?
In December 2025 an attacker used a Cadence runtime bug to duplicate tokens. Flow Foundation says about USD 3.9 million was moved off-network, the network was halted and restored on 29 December 2025, and no existing user balances were accessed.
Is native USDC available on Flow?
No. Circle ended USDC on Flow (Cadence) on 3 September 2024, and Flow is not on Circle's current native USDC list.
How do I check a Flow address for AML risk?
Copy the public address, open one of the services listed above that supports Flow, 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
- Flow Developer Portal — Accounts. Checked 4 Oct 2026.
- Flow Developer Portal — Network Information. Checked 4 Oct 2026.
- Flow Developer Portal — Accounts (Flow EVM). Checked 4 Oct 2026.
- Flow Developer Portal — Accounts. Checked 4 Oct 2026.
- Flow — How Crescendo exceeded expectations (16 Sept 2024). Checked 4 Oct 2026.
- Flow Foundation — Flow Security Incident 27th December: Technical Post-Mortem (6 Jan 2026). Checked 4 Oct 2026.
- Flow Foundation — Flow Security Incident 27th December: Technical Post-Mortem (6 Jan 2026). Checked 4 Oct 2026.
- Flow Foundation — Flow Security Incident 27th December: Technical Post-Mortem (6 Jan 2026). Checked 4 Oct 2026.
- Flow Foundation — Final remediation update regarding the Flow security incident: 87.4 billion counterfeit tokens have been destroyed (30 Jan 2026). Checked 4 Oct 2026.
- Circle — Circle is Discontinuing Support for USDC on Flow (Cadence) Due to the Chain's Upcoming Network Upgrade (5 Aug 2024). Checked 4 Oct 2026.