Risk view
High risk
Very low liquidity
Live token report
Debounce Subnet (DB)
BASE | 0x8d17a46Ee7297CbE14ead574C83466A7385FA970
dead
Track the exact Debounce Subnet token address, live risk score, current status, liquidity, trading activity, and related scanner pages on FreshTokenWatch.
dexbackfillPair age: 10 daysLast seen: 10d agoDead for 9d
FlowRisk 8035.48 vol- liq
RetentionSave DB To WatchlistBring this token back into your repeat workflow and alert loop.MonetizeUse Pro For Faster Follow-UpTurn interesting token pages into a faster scanner and alerts setup.
Health view
Weak market profile
Low liquidity, low volume, or thin transaction flow make this token fragile right now.
Lifecycle
Token is currently marked dead
Latest lifecycle state: dead. Main recorded reason: Published token lost almost all liquidity, volume, and trades.
DeadApr 28, 2026, 3:20 AM
Risk score
80/100
High risk
This is the current risk snapshot from the latest crawl. Lower is better. It reacts to liquidity, transaction activity, volume, valuation balance, and detected red flags.
Health score
14/100
Weak market profile
Low liquidity, low volume, or thin transaction flow make this token fragile right now. This score uses the latest available liquidity, 24h volume, 24h transactions, token age, and current risk score.
Price
$0.00
Liquidity
-
24h volume
35.48
24h transactions
1
Last seen
10d ago
Stale snapshot
Quick verdict
Avoid for now
Risk 80 / Health 14This token is already marked dead in the latest snapshot. Treat it as a failed or broken setup unless a later recovery is visible.
Best next action
Open explorer and verify contract behavior
Most important signal
Very low liquidity
Check next
Use these as the immediate next checks before trusting the token.
Liquidity is thin
Wait for deeper liquidity before trusting price action. Thin pools can move violently and are easier to manipulate.
Trading activity is still weak
Check whether buys, sells, and unique transactions keep building. A token with weak flow can fade quickly after first attention.
Review the flagged risk signals
The crawler already detected very low liquidity. Open the explorer and pair page before assuming the setup is clean.
Simple summary
Debounce Subnet (DB) is a 5h old token on BASE with token address 0x8d17a46Ee7297CbE14ead574C83466A7385FA970, risk score 80, and warning status. FreshTokenWatch currently tracks 1 recorded 24h transactions, liquidity around low, and 24h volume near $35.
Key concern
The score is high mainly because of Very low liquidity and low liquidity.
Signal
Very low liquidity
Signal
Low 24h trading volume
Signal
Token launched very recently
Signal
Very low activity (not dead yet)
Token address
0x8d17a46Ee7297CbE14ead574C83466A7385FA970
Token ID
base__0x8d17a46ee7297cbe14ead574c83466a7385fa970
Status
dead
Pair age
10 days
Source
dexbackfill
Seen
10d ago
Record updated
9d ago
Scanner routes
The main internal routes for this token. Each link appears only once to keep the page cleaner.
Freshness and historical context
Latest crawler sighting
10d ago
This is the last time the crawler refreshed the market snapshot for this token.
Record state
Stale snapshot
Published tokens stay visible in the database even when live activity weakens or disappears.
Tracked pools
Multiple pools are stored per token. The scanner prefers pools with real trade activity before a token is surfaced.
dexbackfillPrimary poolLive trades
0xfFB1DC2bA0d43Ea0a36c91fEadc199e64B68EEBd
Liquidity
-
24h volume
35.48
24h txns
1
Last seen
10d ago
Risk trend
Only one snapshot collected so far.
This is not a live candle chart. It shows how the risk score changed across the most recent stored crawls.
Only one snapshot is available so far. The trend line will fill in after more crawls.
Useful details
Created
Apr 26, 2026, 9:32 PM
Published
Apr 27, 2026, 3:17 AM
FDV
-
FDV / liquidity
N/A
Dead reason
Published token lost almost all liquidity, volume, and trades
Lifecycle
Dead: Apr 28, 2026, 3:20 AM
Revived: Unknown
Archived: Unknown
Live pair chart
Learn these checks
These glossary pages explain the exact risk and market terms that matter for this token report.
Token Address
Using the wrong token address is one of the fastest ways to buy the wrong asset or a copycat contract.
Risk Score
It helps prioritize review, but is not investment advice.
Trading Volume
Volume helps distinguish real market interest from inactive or abandoned pairs, though it can still be manipulated.
Liquidity Pool
Pool depth affects slippage, execution quality, and whether a token has a real market at all.
Dead Token
Dead-status tokens are useful to identify because low activity can make exits hard even if the contract still exists.
Scam Token
Recognizing scam-token patterns quickly helps avoid bad entries and reduces the chance of interacting with hostile contracts.
Related tokens
COCKROACH github.com/cockroachdb/COCKROACH (COCKROACH)
BASE • Risk 16 • Vol 179.12K
Address: 0xADF040c053548D02e581Ac1fcfB0b5e03a15a320
COCKROACH github.com/cockroachdb/COCKROACH (COCKROACH) is a 54d old token on BASE with token address 0xADF040c053548D02e581Ac1fcfB0b5e03a15a
INFLUXDB github.com/influxdata/INFLUXDB (INFLUXDB)
BASE • Risk 16 • Vol 178.75K
Address: 0xADF11a532448fa500827cE858F0706c1D5ff5418
INFLUXDB github.com/influxdata/INFLUXDB (INFLUXDB) is a 55d old token on BASE with token address 0xADF11a532448fa500827cE858F0706c1D5ff5418,
MONGO github.com/mongodb/MONGO (MONGO)
BASE • Risk 26 • Vol 70.9K
Address: 0xADF9AFd4FA1dFeF7a06a7Cd56140af14a4DC2860
MONGO github.com/mongodb/MONGO (MONGO) is a 55d old token on BASE with token address 0xADF9AFd4FA1dFeF7a06a7Cd56140af14a4DC2860, risk score
TIMESCALEDB github.com/timescale/TIMESCALEDB (TIMESCALEDB)
BASE • Risk 38 • Vol 46.54K
Address: 0xADFe69E50d832EE96B827b9e614c49541d7d9F2F
TIMESCALEDB github.com/timescale/TIMESCALEDB (TIMESCALEDB) is a 20d old token on BASE with token address 0xADFe69E50d832EE96B827b9e614c49541
HANDBRAKE github.com/handbrake/HANDBRAKE (HANDBRAKE)
BASE • Risk 62 • Vol 21.89K
Address: 0xADF32c102227DC786DEFD3496163D5Faf6ad1C1F
HANDBRAKE github.com/handbrake/HANDBRAKE (HANDBRAKE) is a 35d old token on BASE with token address 0xADF32c102227DC786DEFD3496163D5Faf6ad1C1
basedbitch (BASE)
BASE • Risk 50 • Vol 18.43K
Address: 0xa6A6763e6e4188f8A03B294D654Da1Ec56C36118
basedbitch (BASE) is a 1d old token on BASE with token address 0xa6A6763e6e4188f8A03B294D654Da1Ec56C36118, risk score 50, and warning status
GOODBYEDPI github.com/valdikss/GOODBYEDPI (GOODBYEDPI)
BASE • Risk 62 • Vol 14.56K
Address: 0xADF06e115d772c350125cF75Ad7B72962F63634b
GOODBYEDPI github.com/valdikss/GOODBYEDPI (GOODBYEDPI) is a 35d old token on BASE with token address 0xADF06e115d772c350125cF75Ad7B72962F636
X1000XLiquidBGT (LIQUIDBGT)
BASE • Risk 72 • Vol 5.9K
Address: 0xa604FD198fA95792243263008BEA7e7dC21f4Bd7
X1000XLiquidBGT (LIQUIDBGT) is a 11h old token on BASE with token address 0xa604FD198fA95792243263008BEA7e7dC21f4Bd7, risk score 72, and war
Token FAQ
What is the DB token address on BASE?
The tracked DB token address on BASE is 0x8d17a46Ee7297CbE14ead574C83466A7385FA970. FreshTokenWatch shows the exact contract address in the page content so users can verify they are looking at the right token.
Is DB on BASE safe?
DB currently has a FreshTokenWatch risk score of 80/100 and a dead status. That is not an endorsement or a guarantee. It is a live scanner snapshot based on liquidity, volume, activity, valuation balance, and current red flags. The main concern right now is very low liquidity
How should I verify the DB contract before trading?
Verify the token address 0x8d17a46Ee7297CbE14ead574C83466A7385FA970, compare the token against the scanner history, review liquidity and 24h transaction activity, and open the external explorer or DEX pair pages before acting.
Browser notifications are not supported here.
Add tokens from the token page to start alerts.
Open another token page and it will appear here.