Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-09-02 20:28 UTC |
| Creator | CT4X7XJiNwBXVC1WBbmAHmbc8G5d3r6svtrrtLhw91Xf |
| Creator took | 0.1% of supply in the first block |
| Outside buyers | 2 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 0 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | yes |
| Recorded from | 28AaXRiagkoEJhPBtKsFiD… slot 443,788,172
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-02 20:28:25 UTC Slot 443,788,172, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | No buyer, 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-02 20:29:56 UTC +1m 31s
2.836e-8 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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. |
| This ticker | On 214 launches from 185 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Let That Sink In |
| Description | We need a runner and i just found the perfect narrative with no bonders now "Let the sink in" |
| Metadata held | sha256 67ba615fa76af2c619666d25eaa050826c1d7b6aa44fd3953dfb96bcd67da6e6 · 455 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. |
| Picture held | sha256 4c3390540f6067d92c0144697fa848c180b603a3c6f28549341f1e4ad3db87c1 · 7,205 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 23:52 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.