Risk view
Watch closely
Very low liquidity
Live token report
Vampire Fortress Claiming Siege (Vam)
BASE | 0x2702b53D6148C4628d6E755d0ca149947C3aa9d1
dead
Track the exact Vampire Fortress Claiming Siege token address, live risk score, current status, liquidity, trading activity, and related scanner pages on FreshTokenWatch.
dexbackfillPair age: 3 monthsLast seen: 3mo agoDead for 3mo
FlowRisk 620.4 vol187.53 liq
RetentionSave Vam 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.SponsorBuy A Labeled Token-Page PlacementRelevant tools and projects can request clearly marked sponsor inventory.
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 15, 2026, 8:13 PM
ArchivedMay 15, 2026, 8:23 PM
Risk score
62/100
Watch closely
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
25/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
187.53
24h volume
0.4
24h transactions
1
Last seen
3mo ago
Stale snapshot
Quick verdict
Avoid for now
Risk 62 / Health 25This 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
Vampire Fortress Claiming Siege (Vam) is a 9d old token on BASE with token address 0x2702b53D6148C4628d6E755d0ca149947C3aa9d1, risk score 62, and warning status. FreshTokenWatch currently tracks 1 recorded 24h transactions, liquidity around $188, and 24h volume near $0.
Key concern
The token is not marked dead, but one or more market signals are still weak, so it should be watched rather than trusted.
Signal
Very low liquidity
Signal
Low 24h trading volume
Signal
Very low activity (not dead yet)
Token address
0x2702b53D6148C4628d6E755d0ca149947C3aa9d1
Token ID
base__0x2702b53d6148c4628d6e755d0ca149947c3aa9d1
Status
dead
Pair age
3 months
Source
dexbackfill
Seen
3mo ago
Record updated
2mo 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
3mo 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
0xdd952fa259393db06fca0eada9e621689ce6a78a6076b075f000946b5908020e
Liquidity
187.53
24h volume
0.4
24h txns
1
Last seen
3mo ago
Risk trend
Apr 10, 2026, 5:18 PM to Apr 14, 2026, 8:03 PM (5 recorded snapshots)
This is not a live candle chart. It shows how the risk score changed across the most recent stored crawls.
Green dots mean active, yellow warning, red dead.
Useful details
Created
Apr 5, 2026, 7:41 PM
Published
Apr 10, 2026, 5:18 PM
FDV
190
FDV / liquidity
1.01x
Dead reason
Published token lost almost all liquidity, volume, and trades
Lifecycle
Dead: Apr 15, 2026, 8:13 PM
Revived: Unknown
Archived: May 15, 2026, 8:23 PM
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.
Liquidity Lock
A lock is a positive signal, but not a full security guarantee.
Related tokens
Vitalum (VAM)
BASE • Risk 80 • Vol 167.14
Address: 0xCFaF48Ff20E1E32d94E47fc2E5520609E7EA919A
Vitalum (VAM) is a 3h old token on BASE with token address 0xCFaF48Ff20E1E32d94E47fc2E5520609E7EA919A, risk score 80, and warning status. Fr
Volatile AMM - VIRTUAL/AERO (vAMM-VIRTUAL/AERO)
BASE • Risk 62 • Vol 4.16
Address: 0x8B49c7eC53Cb4CA3666bB16727FC5C5F6d12226f
Volatile AMM - VIRTUAL/AERO (vAMM-VIRTUAL/AERO) is a 3d old token on BASE with token address 0x8B49c7eC53Cb4CA3666bB16727FC5C5F6d12226f, ris
OvamAI (OVAM)
BASE • Risk 50 • Vol 2.13
Address: 0x0A6F68F27E261A1ad1759B9fe4420AdbE75fFB07
OvamAI (OVAM) is a 2d old token on BASE with token address 0x0A6F68F27E261A1ad1759B9fe4420AdbE75fFB07, risk score 50, and warning status. Fr
🧛🏻♀️ VAMPIRE 🧛🏻♀️ (vampire)
BASE • Risk 62 • Vol 0.13
Address: 0x563BF4D3c7DC4f9F242a42D6eA6CA3dF202fBca3
🧛🏻♀️ VAMPIRE 🧛🏻♀️ (vampire) is a 183d old token on BASE with token address 0x563BF4D3c7DC4f9F242a42D6eA6CA3dF202fBca3, risk score 62,
Vampire (VAMPIRE)
BASE • Risk 62 • Vol 0.05
Address: 0xff871fbac2e2215BDdF3241fE1BF7d54C12ceb07
Vampire (VAMPIRE) is a 55d old token on BASE with token address 0xff871fbac2e2215BDdF3241fE1BF7d54C12ceb07, risk score 62, and warning statu
VAMOS (VMS)
BASE • Risk 80 • Vol 0.03
Address: 0x13b93b9fd986d98fDf3D166C0fE6FfbFd2bA0aBC
VAMOS (VMS) is a 0h old token on BASE with token address 0x13b93b9fd986d98fDf3D166C0fE6FfbFd2bA0aBC, risk score 80, and warning status. Fres
Vampire Strider (VAMPIRE )
BASE • Risk 62 • Vol 0.02
Address: 0x270aff593428B3b4434eC34BC9e76C4631644b07
Vampire Strider (VAMPIRE ) is a 55d old token on BASE with token address 0x270aff593428B3b4434eC34BC9e76C4631644b07, risk score 62, and warn
30k y 29 dias para hacer un maratón con hace 2 meses el panita lo veía muy difícil y dudaba si hacerlo en tan poco tiempo, hoy vamos agarrando un ritmo mejor y sin cansarnos 🙌🏽 no hay mejor cosa que ser 1% mejor cada día y confiar en uno mismo🦍 #on3p3rcent #maraton #running #blog (30k y 29 dias para hacer un maratón con hace 2 meses el panita lo veía muy difícil y dudaba si hacerlo en tan poco tiempo, hoy vamos agarrando un ritmo mejor y sin cansarnos 🙌🏽 no hay mejor cosa que ser 1% mejor cada día y confiar en uno mismo🦍 #on3p3rcent #maraton #running #blog)
BASE • Risk 62 • Vol -
Address: 0xA87a381b8e1ebAFA224f27b45278cF3f73Ab1Bdb
30k y 29 dias para hacer un maratón con hace 2 meses el panita lo veía muy difícil y dudaba si hacerlo en tan poco tiempo, hoy vamos agarra
Token FAQ
What is the Vam token address on BASE?
The tracked Vam token address on BASE is 0x2702b53D6148C4628d6E755d0ca149947C3aa9d1. FreshTokenWatch shows the exact contract address in the page content so users can verify they are looking at the right token.
Is Vam on BASE safe?
Vam currently has a FreshTokenWatch risk score of 62/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 Vam contract before trading?
Verify the token address 0x2702b53D6148C4628d6E755d0ca149947C3aa9d1, 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.