Skip to main content
An account is an address on a chain, a wallet or a contract:
  • Uniswap’s Factory on ethereum, 0x1f98431c8ad98523631ae4a59f267346ea31f984
  • the USDC-WETH pool it deployed, 0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640
Registry gives an address its type, its project and its label. Addresses appear as columns on the other sections: from_address and to_address on transfers, account_address in the balance functions, sender_address on the sender table. Where an account is a contract, Contracts has its deployment, and the two registries join on account_id.

Coverage

Every chain we label accounts on.
alephzeroevmalgorandaptosarbitrumavalanchebaseberachainbitcoinblastbobbobanetworkbsccardanocelocitreaethereumfantomflowflowevmfraxtalgnosisgravityalphahederahederaevmhyperevmimmutablezkevminjectiveinjectiveevminkiotaiotexkatananetworklineamantamantraevmmegaethmonadmovementnearopbnboptimismosmosisplasmapolygonripplerobinhoodchainroninrootstockscrollseievmsolanasonicstacksstarknetstellarsuitempoterratontronunichainvictionworldchainxaixdcxlayerzksyncera

Tables

Registry holds the identity table: one row per attributed address, with the chain it sits on, the project behind it, its type and its label. Activity hours holds the transaction counts and native value behind region, by address, chain, date and hour. Activity coverage holds the share of each chain’s daily activity that is attributed and regioned, by sender, transaction and value. Region distribution holds region as a distribution, by chain, trailing 90-day window, region and confidence, across every sender on the chain, attributed or not β€” it is the only place an unattributed sender’s region appears. Region hit rate holds how often the derived region matches the expected band for attributed accounts whose band is known in advance.