Addresses & Labels
Open a labeled address in TraceFast →

Every address opens at one URL — /entity/{address} — whether it is a wallet,
a contract or a token. The Entity Page documents that page
in full: its tabs, feeds, graph and deep links. This page is about the layer
on top of the chain data: who the address is, how sure we are, and which
statements are attributions rather than proofs.
Finding an address
Search (⌘K) accepts an address, a transaction hash or a block number. You can also arrive by clicking: every counterparty, holder, deployer, implementation and feed row in the app is a link to that address's page, so following a flow is a chain of clicks rather than a chain of copy-pastes.
Identity
The line under the hash is what the platform is willing to say about identity:
- Name — Binance 14 (Hot Wallet), Circle: USDC Token — from the labelling layer, with a verification mark only where the data says verified. An unlabeled address shows its hash and nothing more, which is a statement in itself. Names, tags and risk flags are shown to signed-in readers; a reader who is not signed in sees the hash and a line inviting them to sign in, while kind, chain facts and behaviour signals stay visible to everyone.
- Kind — one word for what the address is:
Address,Contract,Token,NFT token,Multi-token,Smart account. It comes from proven chain facts, not from the label, so a token nobody has named still reads as a token. - Entity — the organisation an address belongs to. One entity typically spans many addresses; see Labels & Entities for how names, categories and attributes are assigned, and with what confidence.
Behaviour signals
Under the name sits a row of quiet, square-cornered signals — observations about behaviour and scale, deliberately shaped differently from the amber chain-fact chips above them, because they make a different kind of claim. Most of them lead to the tab that shows the evidence:
| Signal | What it means |
|---|---|
High traffic | Very high transaction volume (≥ 100,000 transactions) |
Whale | Large native ETH balance (≥ $1M) |
New | First seen on-chain within the last ~30 days |
Beside the key numbers, a liveness chip answers a separate question: Active — activity within the last year, counting transactions, internal calls, events and token transfers alike — or Dormant when there has been none of any kind for over a year.
Attributions are not proofs
Two rows sit next to each other on the page and they are not the same kind of statement:
- Chain facts are derived from chain data: what the address is, what its code does, where it has appeared. They are stated only when proven — see Chain facts.
- Labels — names, entities, categories, risk marks — come from the labelling layer, not from on-chain strings. They carry a source and a confidence, and a name is an attribution: useful, checkable, and not the same as a proof.
Compliance context
If an address appears as a blacklisted subject in a token contract, the page says so in one line — and says what it is not: a listing by an arbitrary token is not a sanctions designation. Open the check to see which issuers, with their authority context, in Blacklist Monitoring. An address absent from every tracked blacklist is still worth reading in full; a clear result is a statement about the tracked corpus, not a general screen.
Deep links
The tab, the section and the filters live in the URL, so a view is shareable as you found it:
https://tracefast.xyz/entity/0x…— the addresshttps://tracefast.xyz/entity/0x…?tab=transfers— straight to token transfershttps://tracefast.xyz/entity/0x…?tab=storage— straight to storage activityhttps://tracefast.xyz/entity/0x…?atBlock=20000000— read it as of a past block
The full parameter list is on the Entity Page.
Related pages
- Entity Page — the page itself, tab by tab
- Labels & Entities — how names, categories and confidence work
- ETH Flows — labeled addresses in live motion
- Blacklist Monitoring — the compliance corpus behind the line above
- Address attribute dictionary — the same chain facts over the API
Last updated 22 Oct 2026, 08:06 UTC · verified against TraceFast v1.0.261 · Markdown