Who is connected to whom by RNBW transfers. Built from every event of the token since its birth, not from a sample. Drawing all twenty-five thousand addresses at once is not possible — the result is a dark blob with no structure — so here are two readable cuts of the same data: the overall movement, and the network of the largest.
Every address is collapsed into one of six classes. Line thickness is the volume that passed through, circle size is how many addresses the class holds. Hover a line to see the number.
Issuance is the zero address, through which the token appears and is burned. It is not a holder and takes no part in holder lists.
Three hundred addresses with the highest turnover and the links between them. Dot size is turnover, colour is the class. Hover to see the label and balance; click to open the address in the explorer.
Only links between addresses inside this group of three hundred are shown, and only those carrying at least one five-hundredth of the largest link. Without a threshold the picture would be overgrown with hairline strokes that hide the structure.
Pictures of connections read with more confidence than the data warrants. Three boundaries not to cross.
This is the main one. Two addresses joined by a line are two addresses between which a transfer went, and nothing more. Exchange deposits, liquidity pools and routers connect everyone to everyone: thousands of people who are strangers to each other pass through one hot wallet. The conclusion "these addresses belong to one person" does not follow from such a graph — and that is the main way pictures like this mislead.
Dot size shows how much of the token passed through an address, not how much sits on it. A pass-through address with a zero balance can be larger than any genuine holder. The balance is shown separately, in the tooltip on hover.
One person holds several addresses, and thousands of people stand behind a single exchange address. Three hundred dots in the picture are three hundred addresses, and counting them as three hundred participants is wrong.
From block 41349994 to the head of the chain. Each transfer yields an edge "sender → recipient"; identical pairs add up, so an edge holds the total that passed and the number of transfers. The pass is resumable: it saves state along the way and continues from where it stopped.
Exchanges, liquidity pools, Rainbow contracts and other contracts are recognised by labels gathered from several open sources at once. An address with no label counts as an ordinary wallet — and most often that is exactly what it is.
The placement of the dots is a force method: nodes repel each other, links pull together. It is computed once per rebuild, not in every reader's browser: for three hundred nodes the calculation takes seconds and freezes a phone's tab, while the result is the same for everyone. The starting arrangement is a circle rather than random — otherwise the picture would shift on every rebuild where the data had not changed at all.
Why not the whole graph. The token's history holds close to two hundred thousand unique sender-to-recipient pairs. Such a layout produces one solid blob in which nothing can be read, weighs megabytes and takes tens of seconds to compute in a browser. This is a known limit of the genre, not an omission: past a certain number of nodes a picture of connections stops being a picture. Hence the collapse into classes and the top by turnover — two cuts, each answering its own question.
Recomputed once a day. Served as /api/graph_groups.json and /api/graph_top.json.