ANC
The creator took 37% of supply at 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.
noteThe creator took 37.0% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 2.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 03:22 UTC |
| Creator | G8474uBXswC5qYZCYbzNu8EaTvfjzXqgujazrCB2hKLt |
| Creator took | 37.0% of supply in the first block |
| Outside buyers | 1,122 distinct wallets, not counting the creator, bought on the bonding curve: 141 within the first 30s, 5 bundled into the creation block. |
| Graduated | 3.8 h after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | yes |
| Recorded from | 2i4AFV4inySuqqN1ket86C… slot 452,487,724
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 03:22:52 UTC Slot 452,487,724, 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. |
| Thirty seconds in | 141 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. |
| Curve completed | 2026-10-02 07:09:34 UTC +3h 46m 42s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 07:09:34 UTC +3h 46m 42s
4.109e-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. |
| This ticker | On 10 launches from 10 creator wallets, including this one. See them → |
| This creator | 1 earlier launch, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 5 other creator wallets, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 2.7 SOL |
| Read from chain | 2026-10-02 16:08 UTC, just now |
What this launch claimed to be
| Name | Anchor |
| Description | Built against snipers, whales, bundles & vamps. |
| Metadata held | sha256 8d4784e85a3328fa2d78aa6b8e2750b2db0d09e13c707bdc12dd39ec758b8fd2 · 420 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 43d911aeebcfdf3c06dfc7f67ae2cc1e577933b598f54de49e3b0df58acb4ac8 · 298,346 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 03:22 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.