HIKSY
The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
findingOnly 5 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteThe creator sold while we were watching.
noteOnly 3.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-18 10:53 UTC |
| Creator | Gm27cfTyWkiE5K3CE3PLsjoKbtueRkoxBUDFasAAz5wK |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 5 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | yes |
| Recorded from | 3Jqv8Sr1TAPNJTs9e5pcVW… slot 448,062,220
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-18 10:53:29 UTC Slot 448,062,220, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-18 10:53:29 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 10 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
| Highest price seen | 2026-09-18 10:54:40 UTC +1m 12s
6.626e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | No other launch we hold a picture for used this one. |
Pool
| Liquidity | 3.5 SOL |
| Read from chain | 2026-09-20 03:02 UTC, just now |
What this launch claimed to be
| Name | Hiksy |
| Description | A cool beaver with shades and a confident attitude ready to rule the day |
| Metadata held | sha256 29c8af53900ebfc4af692775da48d09d9f8f5b4198b70d6b7e43d98145720388 · 411 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-19 10:55 UTC. |
| Picture held | sha256 ccc1737cd1509a966fcf4cf1ee300759ae7402e2ab7158f79147ef1b2b420bda · 1,929,384 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-18 10:53 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.