Where did it go?

Paste the address you sent to. Nansen labels decide which of four recovery routes you’re on — and draft the ticket.

example 0xe460…bbef — a Binance deposit address

10 Nansen calls · recorded 2026-09-16 · replayed from fixtures/0xe460…bbef.json · 0 credits · 3ea6cfcd752b

Binance deposit address high · direct-labelethereumrecoverable

0xe460774c849089ee3edf0fb06da14c066caabbef

labelled 🏦 Binance: Deposit [0xe46077]swept to 🏦 Binance 14 [0x28c6c0]outflow 100% to 0x28c6…1d60first gas from 🏦 Binance [0x943080]

Burn address high · burnethereumunrecoverable

0x0000…dead

HTTP 422 · Burn address not allowed

Address-poisoning look-alike high · poisonerethereumscam address

0x50b3…eac9

4 of 4 inbound transfers are look-alike to…4 in / 0 out, last 2026-05-30

Your own wallet high · relatedethereumstill yours

0x3ff4…62b0

first funded by 0xb0ae…03b5 on 2026-05-30related wallet · First Funder — 0xb0ae…03b5

+ 9 more recorded verdicts in npm run verify · 13/13 decision hashes reproduce offline

1search/general0 cr
is a token contract deployed at this address?
→ contract route at 0 credits, search over
2profiler/address/transactions1–2 cr
transfers in and out, the sweep hashes; HTTP 422 = burn
→ burn, dormant, poisoning, which txs to look up (+1 cr all-time page when quiet)
3profiler/address/counterparties5 cr
who it pays and how much of the outflow
→ 100 % to one wallet = the sweep signature
4profiler/address/related-wallets1–2 cr
Deployed by, Created by, First Funder relations
→ contract vs your own wallet (+1 cr on your address)
5profiler/address/first-funder1 cr
who paid its first gas, and in which tx
→ exchange gas dripper vs you
6transaction-with-token-transfer-lookup1 cr × ≤4
entity labels on the transfer: 🏦 Binance: Deposit
→ the route