Token markets

Compare prices and trading activity on Robinhood Chain. One row per token address.

JSON API guide

Search all recorded contracts. Also accepts shortened addresses, stock ISINs and pool addresses or IDs.

Tokens: All tokens

Sort: 24h volume

Direction: Descending

Descending
Ascending

Trust: All verdicts

Activity: Any activity

Readings: All readings

Depth: Any depth

Identity: All contracts

Search: NOM Reset all

Matching contracts (328)Across the registryShow results

Search includes recorded contracts outside the tracked markets. Open a contract to inspect its readings. Market filters below apply to the market table.

NOMNom community
0x761d4af1…bb5977770x761d4af18fd8f7b430cab4d751ce7a83bb597777
Contract metadata. Observed 13 d ago.
View market
NOMNOMINAL 1969 community

Tracked market readings

Scroll sideways for volume, market cap and catalog status.

No token matches these filters on this page. Remove a filter or return to page 1. Activity and data filters require current observations, so an unread token may be excluded.

ExploreMost traded Community activity 100+ daily swaps Current market data Compare names

Filters combine. Activity uses the selected pool's complete 24-hour window. V3 quote holdings and V4 depth measure different things.

Sources, coverage and table definitions

Identity badges describe address checks. Price and volume describe each token's selected pool. Volume requires a complete 24-hour window of valued swaps. Market cap is an estimate from supply evidence and the selected price, not a measure of freely circulating supply.

Every reading shows its source and age. Unavailable data stays unavailable. Crypto catalog matches use tickers, not contract addresses; Stock Tokens have a separate catalog.

Individual pools Filter definitions as JSON

Robinhood crypto catalog · needs attention · 11 d ago

Fletch checks the public crypto catalog every 15 seconds. It covers crypto availability; Stock Tokens have a separate asset list. A price feed does not mean trading is available.

The sync is stale. The last known snapshot is retained.

The endpoint is unofficial and can restrict access. Responses can vary by client. These are observed catalog fields, without an endorsement or a prediction of future trading.

Watch catalog changes