Graph & projections

The Graph tab is not one picture. It is several projections of the same address, each answering a different question, drawn by one canvas. The strip lists the projections this address actually has, in the order that fits it: a wallet opens on Ledger, a token contract on Semantic.
The projections
| Projection | What it draws |
|---|---|
| Ledger | Value moved around this entity — token and ETH transfers, with whom and how much |
| Semantic | Structural relationships — deployer, implementation, same bytecode, protocol membership |
| Operations | Interpreted actions — swap, supply, bridge — rather than raw transfers |
| Behavior | Recurring on-chain patterns over time |
| Intent | A single user intent across an ERC-4337 UserOp |
Operations lists, under the canvas, the protocol actions it decodes. An action on a protocol that is not on the list leaves no operation on the canvas — that is the view's coverage, not a statement about the address.
A projection that cannot be drawn for this address is not hidden and not faked: it stays in the strip, marked, and clicking it explains why — "This projection was built, but there are no connections in this window", or that it was not computed, or that it does not apply here. The tab that opens by default is one that can actually be drawn, so you never land on an empty canvas that reads as "nothing happened".

The window
Value projections are always windowed — a graph of all history would be a
hairball, and an unnamed window would be a lie. The header states the slice in
blocks (latest slice 26,170,360–26,220,360) and steps through it: previous,
next, wider, narrower. In the URL, gFrom and gTo set it explicitly, and an
explicit pair outranks the page's own epoch. The window applies to Ledger and
Operations; Semantic is not drawn for a window — it shows the structure as it
is now, and says so.
Above the canvas, Ledger summarises what was drawn from: how many counterparties, how many movements in how many transactions, the ETH and token volume, and over what period.
The activity axis
Over the Ledger canvas runs an activity strip: every movement of the address over its whole life, counted per run of blocks — 500,662 movements · first at block 318,074 · last at block 26,220,130. Bar height is on a log scale, so a single movement stays visible. On an address the bars are split by kind — token transfers, ETH transfers, internal transfers — with a lifetime total for each; a token's axis counts its own transfers. The highlighted band is the window drawn below, and clicking a bar opens those blocks as the window. The stretch past the last counted block is marked not read yet. For a token with hundreds of millions of transfers the axis gives way to a sentence with the count.
Reading and shaping the graph
- Layout — left-to-right or top-to-bottom.
- How many — top 5, top 10, top 20 or all counterparties.
- hide dust — drop movements below the significance floor. The floor is a
dollar value (
minUsdin the URL,minUsd=0to keep everything); without it a busy token's window fills with spam-sized transfers. - verified only — keep counterparties the labelling layer has verified.
- unhide / undo / redo — nothing you filter away is lost; every step is reversible.
- Zoom, fit and node expansion — expanding a node pulls in its own movements, so a trail can be followed without leaving the canvas.
Under the canvas, the status line says exactly what you are looking at:
11 nodes / 10 edges · 2 dust hidden · 92 unpriced kept. Anything the filters
removed is counted there rather than silently dropped — including the honest
awkward case, a counterparty whose value could not be priced but which is kept
anyway.
Each edge carries what it is made of — 957 transfers · 110 tokens — and the
address you came from is marked as THIS ADDRESS so the centre of the picture
is never ambiguous.
Exports
The graph exports as PNG for a report. A full-screen mode (⇧F) gives the canvas the whole window. For the same relationships as data, use the public API.
One thing the graph does not claim
Identity and risk marks on the nodes are as of today, not as of the window. The picture is historical; the names and warnings on it are current. The page states this under the canvas, because the alternative — labelling a 2023 window with 2023 attributions — is not something the labelling layer can honestly reconstruct.
Related pages
- Entity Page — tabs, header and URL parameters
- Accounts & Wallets — counterparties as a ranked list
- Transaction feeds — the rows behind the edges
- Labels & Entities — what "verified" means on a node
Last updated 22 Oct 2026, 08:06 UTC · verified against TraceFast v1.0.261 · Markdown