Degen $degen

These charts are HEY’s own readings. Before 2026-09-13, price and volume come from GeckoTerminal’s daily candles (provider archive, read 2026-10-02), used only beside a ship and on the Terminal chart; the archive holds no liquidity or valuation.

Price and liquidity are the day's last reading from the source that ranked highest that day. Trades and volume are decoded from the chain by decoding the chain's own trades where HEY has them, the aggregator's rolling 24 h figure otherwise. Counts of trades, transfers and events, never of accounts.

Lifecycle

Pool created

2026-09-18 (43d ago)

Launch stage

Trading in a DEX pool

First trade in HEY’s trade index

2026-07-17

Last trade in HEY’s trade index

2026-10-30

Token first seen by HEY

2026-09-02

First price reading by HEY

2026-09-13

DEX stage recorded by HEY

2026-09-14

Daily candles from GeckoTerminal’s archive (not HEY’s readings)

2026-07-17 to 2026-08-04 · read 2026-10-02

Highest liquidity held two days running

$290K · now 66% of it

HEY's trade index decodes the chain's own trades one closed UTC day at a time, so the day in progress is not in it yet. The dates HEY recorded are listed in the order they happened; HEY can read a pool's price before its launch-stage check records the stage.

Market integrity

What happened to the token's market in HEY's own readings, each with its day and source. It describes the market, never whether development stopped.

Distribution

Holder count and concentration not measured — the holder source returned only balances that changed in the last few days, which cannot account for the supply.

The largest balances of this token, drawn to scale. Circles that moved the token between each other share a colour and a line. A pool, a launchpad locker and a burn address are usually the biggest balances on this chain, so those are named, left out of the concentration figure, and left out of the lines — almost everyone has traded with the pool, so drawing it would say nothing.

One group of these addresses moved the token between each other in the last few days, so it is drawn together and coloured. That is a fact about transfers. It is not a claim that anyone is the same person, and HEY does not decide what it means.

Read from the chain on 2026-10-29, 2d ago. The holder count is the holder source's, outside pools, lockers and burns; a block explorer counts its own way and can differ. Every circle opens that address on the block explorer. A circle is an address, not a person. HEY does not label wallets, score them or track them across tokens, and none of this affects activity status or any HEY score.

What HEY checked on the contract

• Contract on Robinhood ChainConfirmed by HEY: the contract exists on chain 4663.Chain RPC / decoded trades
• Upgradeable proxyNo proxy pattern detected at the last check: the EIP-1967 implementation and beacon slots are empty and the explorer reports none. A proxy of another design would not show here.EIP-1967 implementation and beacon slots (storage read), explorer proxy report · checked 5d ago
• Deployer0x67d0…b6e1 deployed this token; HEY has seen no other published project's token from it.Explorer contract-creation record · checked 6d ago
• Project stands behind the contractNot yet — HEY has not seen the project name this contract on its own site.Project sources read by HEY
• Launch recordHEY did not observe the launch; the token was found through its trades or a listing.Launch factory / discovery source
• Liquidity against its highLiquidity in the pool HEY's market reading follows is within 34% of the highest level the token held on two consecutive daily closes.HEY market readings
• What can be sold before the price moves 1%About $5.0K across 12 pools, at the last pool reading.Pool depth decoded from the chain
• Addresses that called the contract20 different addresses on the latest indexed day, making 95 calls — 5 each.Contract calls decoded from the chain

Each line is something HEY observed, with where it came from. None of them is a verdict; a noted line is one worth reading before relying on the token.