Token Dashboard
tokens
1960
contracts
6137
confirmed
5685 of 6137
chains seen
14
unmeasured
181
queued
0
All (9173)Waiting for discovery (0)Processed (7376)Rejected (1812)token AZUR ×
PinTokenBridgeBridge txStageDiscovery tookToken entityLabels
#91665 h ago AZURAzuro 0x23d7fe73…f920b4 open portal_bridgeethereum → base 0x19d52d2e…b17a86 processedDISCOVERED 34 s AZUR deployer_burstsymbol_cluster
#91608 h ago AZURAzuro 0x2b4d0fc2…cdf6c0 open portal_bridgebase → ethereum 0x012bf945…2328e8 processedDISCOVERED 27 s AZUR symbol_cluster
#77442 d ago AZURAzuro 0x9e6be44c…edcd5a open base_bridgeethereum → base 0xd0fe16d7…4733fd processedSKIPPED_DUPLICATE 10 h AZUR deployer_burstsymbol_cluster
#40552 d ago AZURAzuro 0x2b4d0fc2…cdf6c0 open base_bridgebase → ethereum 0x34e291bc…0af35a processedSKIPPED_DUPLICATE 4 h 25 min AZUR
Showing 4 of 4 pins (9173 in all)
What the stages, outcomes and labels mean

Stages

rejectedIngest refused the record; the reason is stored and listed below.
waitingAccepted and queued; discovery has not reported an outcome yet.
processedDiscovery reported an outcome, listed below.

Discovery outcomes

DISCOVEREDContracts were found and written: a token entity was created, or an existing one gained a contract or a route.
SKIPPED_DUPLICATEThe token was already known; the pin was linked to the existing entity and no new search was run.
SKIPPED_MAJORThe token is a major (stablecoin, wrapped native); discovery does not search for those.
SKIPPED_NO_SVMA Solana pin arrived while the Solana reader was not configured, so it could not be resolved.
SKIPPED_NO_TOKENThe pin named no token address, and the bridge index could not supply one.
SOLANA_UNRESOLVEDThe Solana RPC could not say which mint the transaction moved; the pin is kept and can be reprocessed.
SKIPPED_BLOCKEDThe mint was blocked outright; discovery wrote nothing.
SKIPPED_EXCLUDEDThe token is excluded: the pin is recorded against it and nothing more is searched.
SKIPPED_DENIEDThe operator detached this contract from the token it would have joined; nothing was written.
NOT_A_TOKENThe address the pin named holds no ERC20 or SPL mint.
UNKNOWNDiscovery could not finish: an index or an RPC did not answer, or the run failed. Not a negative result; reprocess it to try again.
backfilledMarked processed by the progress migration: the token already had a contract or evidence when the tracking columns were added.

Reject reasons

SELF_LOOPSource and destination are the same chain, so nothing was bridged.
UNKNOWN_CHAIN_SLUGThe source or destination chain is not one in chains.json, so nothing could be looked up there.
MALFORMED_ADDRESSThe record failed format checks: an address is not a valid EVM or base58 address, or the record is not the shape the feed promised.
DUPLICATEThe same transfer (chain, transaction, log index) was already stored; there was nothing new to learn.
NOT_A_TOKENThere is no ERC20 or SPL mint at the token address.
KNOWN_MAJORA stablecoin, wrapped native, or another major that is bridged constantly; excluded as noise.
BLOCKEDThe contract was blocked outright. The pin is kept as a tombstone so the refusal stays countable.

Labels

Accepted and sent to discovery like any other pin. Listed under "labelled" because it carries a cluster label, which lowers its priority and never rejects. A pin with two or more labels starts at normal priority instead of high, which only sets how soon discovery and the liquidity check get to it.

round_supplyThe amount sent is a 1 followed by 24 or more zeros in base units (with 18 decimals: exactly 1,000,000 tokens, 10,000,000, and so on): a whole minted supply moving at once.
deployer_burstThe same sender bridged three or more different tokens in the last 24 hours.
symbol_clusterThe symbol is within two edits of another token seen in the last 24 hours: a lookalike.
provider_knownReserved for a token a provider already lists; nothing sets it today.