DexBrief

HunterBot (HUNTERBOT): market history & retirement report

Solana · No market returned by the checked sources

Current market check

HUNTERBOT market now

Saved observation
PriceUnavailable
Market capUnavailable
24h trading volumeUnavailable
Pool liquidityUnavailable

Saved market observation: Not recorded. Refreshes when you visit.

·

Current quotes are separate from the historical report below. Volume and liquidity describe the displayed pool; unavailable fields are not zero.

The finding

Contract-specific market history

HunterBot was archived on July 26, 2026 because 3 catalog lookup checks did not retain a qualifying market for its Solana contract.

Solana · 6dvMip6ppKYchP4DCV5pZ5co16q64CRbw2mN765bpump

Latest dated evidence:

Follow the recorded trend

HUNTERBOT price, market cap and trading activity

HUNTERBOT has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.

HUNTERBOT holder count

42

Sep 01, 2026 12:43 UTC · One recorded value

getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.

HUNTERBOT top-holder concentration

99.86%

Sep 01, 2026 12:43 UTC · One recorded value

getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.

HUNTERBOT supply distribution

HUNTERBOT chain snapshot: September 01, 2026. Account shares can include pools and custodians.

HUNTERBOT: Largest measured entry

98.16%of recorded supply

HUNTERBOT: Top ten measured entries

99.86%of recorded supply

HUNTERBOT: Tracked deployer share

0.00%of recorded supply
The recorded sequence

What happened to HUNTERBOT?

  1. 01First tracked

    Entered the DexBrief catalog.

  2. 02Catalog retired

    no tracked market after 3 checks

  3. 03Follow-up check

    Follow-up inconclusive

  4. 04Follow-up check

    Follow-up inconclusive

  5. 05Follow-up check

    No market returned by the checked sources

  6. 06Follow-up check

    No market returned by the checked sources

  7. 07Follow-up check

    No market returned by the checked sources

First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.

Case findings

HUNTERBOT: findings from the retained record

The provider follow-up for HUNTERBOT

At the October 26, 2026 follow-up for HUNTERBOT, the results were DexScreener: empty; GeckoTerminal: empty. No matching HUNTERBOT market was returned by these completed checks.

What triggered the HUNTERBOT retirement

For HUNTERBOT, the stored decision is "no tracked market after 3 checks". The record counts 3 checks, but does not retain 3 independent provider responses. It cannot establish the date of HUNTERBOT's last trade.

HUNTERBOT: archived market snapshot

The saved market figures for HunterBot are price $0.0000149, 24-hour volume $102.48K, pool liquidity $8.12K, fully diluted value $14.91K, 24-hour trades 3.73K. Those fields lack a complete set of trustworthy observation dates, so they describe the archived HUNTERBOT snapshot and are excluded from dated return calculations. The saved route is 9YFSqW3dJ6XN45RqHzALivTm5QafShF4ehePQ4weohJT. The $14.91K figure is fully diluted value; a circulating market cap was not retained for HUNTERBOT.

HUNTERBOT: recorded holder distribution

The September 01, 2026 HUNTERBOT snapshot records 42 measured holder entries through getProgramAccounts. It separately reports 409 token accounts; that account count is not a count of unique owners. 15 entries exceeded 0.01% of HUNTERBOT supply. That is 35.7% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.86% of supply in that snapshot. The HUNTERBOT concentration figure does not identify which large entries belong to pools, custodians or individual people.

HUNTERBOT supply and contract controls

For HunterBot, the contract fields retained from September 01, 2026 are mint authority: revoked; freeze authority: revoked; token supply: 998,689,420.4577. The tracked deployer held 0.0000% of HUNTERBOT supply at that check. A zero HUNTERBOT balance does not show when or how those tokens left that address. The saved creator profile lists 9 mint(s) and 2 migration(s).

The missing interval in HUNTERBOT's history

For HUNTERBOT, the retained history consists of 1 dated snapshot(s) and 0 daily candle(s). It lacks a comparable price or activity series spanning at least six hours. First tracking is June 06, 2026; catalog retirement is July 26, 2026. An observed decline between those markers cannot be reconstructed from the retained HUNTERBOT values alone.

Source definitions and research methodology

Sources and observations

Latest provider checks

SourceResultChecked (UTC)Pools returnedEvidence
DexScreenerempty2026-10-26 06:35 UTC0exact_contract_lookup
GeckoTerminalempty2026-10-26 06:35 UTC0exact_contract_lookup

Recorded market evidence

Each row is one source and one scope. Pool liquidity and activity are not token-wide totals. Missing fields are not zero. Full history is available in the downloads.

Observed (UTC)SourceScope / exact poolPriceLiquidity24h volume24h trades
2026-09-01 12:43 UTCgetProgramAccountsgetProgramAccountsNot recordedNot recordedNot recordedNot recorded

Research data

HUNTERBOT: 1 dated snapshots, 0 daily candles. Download the retained observations and source records.

Version, license and citation

DexBrief. HunterBot: market history & retirement report. Latest dated evidence: 2026-10-26T06:35:43+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/hunterbot-07c3d26783daa8f3f1b6/

Permanent evidence edition

DexBrief analysis and compilation: CC BY 4.0. Underlying provider data remains subject to its source terms.

Evidence SHA-256: 61414c67864c85b86e9a6e36316efa660fe32affc61e5f19332052ab32e005fa