Filtering Rejection Explorer
The token-level investigation view for understanding exactly which assets a rule rejected. Browse rejection categories, select a reason, search matching tokens, and move from aggregate statistics to concrete examples.
Browse
Category and reason tree
Overview
Top reasons and recent rejects
Inspect
50 matching tokens per page
Actions
Copy mint or open DexScreener
What the Explorer tab is for
Use Explorer before relaxing a rule. Its overview combines the most frequent reasons with recent rejected tokens. Selecting a reason loads the matching token records in pages of 50, with token identity, source, rejection time, mint-copy action, and a DexScreener link for additional market context.
Reading the interface
Each area answers a different operational question. Use the descriptions below before changing a filter.
Reason navigation
The left side organizes the rejection vocabulary into a searchable hierarchy.
Overview
Returns to the summary of top reasons and recent token rejections.
Category tree
Expands groups of related reasons and shows a count beside each exact rule.
Reason search
Filters the tree by human-readable rule label when the list is too large to scan.
Token results
Selecting a reason replaces the overview with the tokens rejected for that exact cause.
Token identity
Shows logo when available, symbol, and name so patterns are easier to recognize.
Source and time
Identifies the filter source and how recently the token was rejected.
Pagination
Move through result pages without loading the entire rejection history into the interface.
Investigation actions
Small actions provide context without turning Explorer into a trading interface.
Copy mint
Copies the token mint for use in other dashboard tools or independent verification.
Open DexScreener
Opens the token on DexScreener for external market and pair context.
How to interpret samples
A rejection reason is only useful when you look at representative examples.
Consistent bad samples
If most examples exhibit the intended risk, the rule is doing useful work even when its count is high.
Mixed samples
If good and bad tokens are mixed, inspect data freshness and threshold boundaries before adjusting the rule.
Recommended workflow
- 1
Open Overview and choose a high-impact reason from Top Reasons or the category tree.
- 2
Inspect recent and older result pages so one market moment does not dominate your conclusion.
- 3
Open representative tokens externally and compare their data with the rejection source.
- 4
Only after sampling the results, move to the matching settings tab and adjust one control.
Practical guidance
- Search reasons by concept such as liquidity, holder, authority, volume, or price change.
- Use recent rejection time to distinguish a persistent issue from a short provider outage.
- Copy mints into Token Details when you need ScreenerBot’s broader on-chain and pool context.
Explorer records why a token failed the configured pipeline; it does not certify that a passed token is safe or profitable.