Entity Page
Open an entity page in TraceFast →
Every address on Ethereum — a wallet, a contract, a token, a proxy, a smart account — has one page in TraceFast:
https://tracefast.xyz/entity/{address}
There is no separate address page, token page or contract page to choose between. You paste an address and get the page for that address; what appears on it follows what is known about it, not what it is called.
The address is case-insensitive (checksummed or lowercase both work), and a string that is not a 20-byte address is refused rather than rendered as an empty page.
By kind
The page is the same; the evidence differs. Each of these covers one shape in detail:
| What it adds | |
|---|---|
| Accounts & Wallets | Balance and nonce, portfolio, top counterparties, validator withdrawals, smart accounts |
| Tokens & Collections | Price and price history, holders, DEX pools, the facts that say what kind of asset it is |
| Contracts | Chain facts, proxy and implementation relationships, storage activity, emitted events |
| Transaction feeds | Everything under the Transactions tab, feed by feed |
| Graph & projections | Ledger, Operations, Semantic, Behavior and Intent views of the same address |
What the header tells you
The line above the tabs is the page's whole claim about identity:
| Element | What it is |
|---|---|
| Kind | What the address is, in one word — Address, Contract, Token, NFT token, Multi-token, Smart account. Absent when nothing has been proven yet |
| Name | The label, where the labelling layer has one — with a verification mark only where the data says verified. Shown to signed-in readers; a reader who is not signed in sees the hash and a line saying that names, tags and risk flags need a sign-in |
| Chip row | The proven facts worth stating up front: Contract, Upgradeable proxy, ERC-20 in code, Privilege used, Controls other contracts, History, and the behaviour signals |
| Block number | The chain head this page was rendered at |
The chips are not a risk score and not an opinion. Each one is a fact that was proven from chain data, and each carries its own sentence when you hover it — including what it deliberately does not claim.
The tabs
The strip groups tabs by the question they answer. Transactions is a group: it opens on the transaction feed and carries everything a transaction did.
| Tab | What it answers |
|---|---|
| Overview | What this address is, since when, and how it is doing |
| Transactions | The transaction feed, and inside it Token Transfers, NFT Transfers, Internal, State Changes, Storage, Events, Deployments and DEX Trades |
| Withdrawals | Beacon-chain validator withdrawals credited to this address — no transaction behind them, so they are not filed under Transactions |
| Holders | Who holds this asset now, ranked by balance |
| Pools | DEX pools this asset trades in, with its volume over the last 7 days |
| Graph | Money flow and structure around this address |
A tab disappears only on a positive fact. Holders and Pools go when the address is known not to be an asset; Events goes when it is known to have never carried code, and Storage goes only when there is no code and no storage history — a self-destructed contract keeps its Storage tab; Deployments goes when the address is known never to have created a contract; Withdrawals appears only where such credits exist. When the answer is simply unknown, the tab stays — hiding it would assert something the platform cannot back, and an empty feed that says "nothing here" is more honest than a missing tab.
Overview
Beyond the header, the Overview stacks these sections, each present only when it has something to say:
- Key numbers — what the row carries follows the address: ETH balance (with its USD value), direct transactions, nonce and a 30-day activity sparkline for an account; price for an asset; state changes and fees paid for both. "Direct transactions" counts top-level transactions only. A liveness chip reads Active (activity of any kind within the last year) or Dormant.
- Compliance line — if a token contract has blacklisted the address, the page says so and says what it is not: a listing by an arbitrary token is not a sanctions designation. See Blacklist Monitoring.
- Chain facts — the full reading of what has been proven, below.
- Relationships — deployer, implementation and its history, proxies delegating here, EIP-7702 delegates, byte-identical code, price feeds quoting it, and — for a lookalike — what it impersonates. Where a direction has no total, the page shows a sample and says so. (Contracts)
- Timeline — first seen and last active against the protocol forks, with the streams that were consulted named.
- Price history — 7 / 14 / 30 days, for an asset with a price. (Tokens)
- Portfolio — token holdings and ETH, with its own "at block" input. (Accounts)
- Top counterparties — who this address keeps meeting, ranked by how often. (Accounts)
- Validators paying out here — validators whose withdrawal credentials point at this address, as of a named epoch. (Accounts)
Chain facts
Chain facts are grouped — Nature, Asset, Architecture, Capabilities, Interfaces, Presence, Derived, Relationships — with a count each, and each fact states in one sentence what it means and at which block it was observed.
Two rules govern the whole card:
- A fact is stated only when it was proven. A fact that is absent was not
proven, which is not the same as "no". A token without a
Mint functionfact is not thereby a token that cannot mint. - A fact says what it says, and no more. "Pause function" means a pause-family function exists in the code that executes — not that the contract is paused now, and not who may pause it.
These are the same facts the public API returns for an address; the ids and their meanings are in the address attribute dictionary.
Reading an address at a past block
Add ?atBlock=N and the page answers as of block N. A banner names the epoch
and — this is the part that matters — names what it does not cover:
At this block: the counterparties, the feeds and the portfolio pane. Current instead: the header metrics, identity, risk and chain facts.
Balances at a past block are shown in ETH and tokens without a dollar figure: dollars for a past moment are the price of that hour, and this reading carries no price of its own — a number multiplied by today's rate would be confidently wrong.
URL parameters
Every view on the page is addressable, so a link carries the reader to exactly what you were looking at.
| Parameter | Effect |
|---|---|
tab= | Which tab to open (transactions, transfers, nft-transfers, internal, state-changes, storage, events, deployments, dex-trades, withdrawals, holders, pools, graph). A value this address has no tab for falls back to the default instead of an empty screen |
focus= | Scrolls to a section of the Overview and opens the tab that renders it |
atBlock= | Read the counterparties, feeds and portfolio as of that block |
cpWindow= | Counterparty window: all, 24h, 7d |
cpFind= | Look up one address in the counterparty list |
gTab= | Which graph projection to open (ledger, operation, semantic, behavior, intent) |
gFrom=, gTo= | The graph's block window — an explicit pair outranks the page epoch |
minUsd= | Transfer-significance floor for the graph, in dollars (0 shows everything, dust included) |
storageSort=, storagePage= | Sorting and paging of the storage feed |
slot= | Opens the change history of one storage slot on the Storage tab |
What happened to the old pages
/entity/{address} replaced the separate per-address pages. The former
/address/{a}, /tokens/{a}, /contracts/{a}, /deployers/{a} and
/implementations/{a} URLs no longer exist and are not redirected — update
any bookmark or integration that still points at them.
To reach an address you already have, paste it into the search (⌘K) — it opens the entity page for it. To find one you don't, start from a list; every row on these opens an entity page:
Deep links off the old pages that carried a ?tab= value still land in
context: the old value names the section that renders that content today.
Related pages
- Addresses & Labels — the identity layer on top of the facts
- Transactions — where a feed row leads
- 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