BWT holder count
146Sep 01, 2026 13:44 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Current market check
BWT market now
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
BWT was archived on August 18, 2026 because 3 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · HdB3FdEqpjnBnFDXGiBjuED2RYsVJFTqwwCY5BfhjgAx
Latest dated evidence:
Follow the recorded trend
BWT price, market cap and trading activity
BWT has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
BWT top-holder concentration
99.10%Sep 01, 2026 13:44 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.BWT supply distribution
BWT chain snapshot: September 01, 2026. Account shares can include pools and custodians.
BWT: Largest measured entry
97.75%of recorded supply
BWT: Top ten measured entries
99.10%of recorded supply
BWT: Tracked deployer share
0.00%of recorded supply
The recorded sequence
What happened to BWT?
- 01First tracked
Entered the DexBrief catalog.
- 02Catalog retired
no tracked market after 3 checks
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
The evidence in this case
BWT: what happened and what the record supports
What triggered the BWT retirement
For BWT, 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 BWT's last trade.
BWT ownership at the last saved chain check
The September 01, 2026 BWT snapshot records 146 measured holder entries through getProgramAccounts. It separately reports 967 token accounts; that account count is not a count of unique owners. 39 entries exceeded 0.01% of BWT supply. That is 26.7% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.10% of supply in that snapshot. The BWT concentration figure does not identify which large entries belong to pools, custodians or individual people.
BWT supply and contract controls
BWT's September 01, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 998,947,100.7909. The tracked deployer held 0.0000% of BWT supply at that check. A zero BWT balance does not show when or how those tokens left that address. The saved creator profile lists 1 mint(s) and 1 migration(s).
The missing interval in BWT's history
The BWT archive currently contains 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 April 10, 2026; catalog retirement is August 18, 2026. An observed decline between those markers cannot be reconstructed from the retained BWT values alone.
Provider checks & full observation table
Latest provider checks
| Source | Result | Checked (UTC) | Pools returned | Evidence |
|---|
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) | Source | Scope / exact pool | Price | Liquidity | 24h volume | 24h trades |
|---|---|---|---|---|---|---|
| 2026-09-01 13:44 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
Download and cite this report
DexBrief. “BWT: retirement and market activity report.” Evidence checked 2026-09-01T13:44:17+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/bwt-0ae700e1d750bcf55e92/
DexBrief’s compiled observations and analysis may be cited with attribution under CC BY 4.0; underlying provider data remains subject to its source terms.
Evidence SHA-256: 583be7af202568a636fb09f3fec1cfc21c38b79a589b2a2d795df91fc1638abb