ANATWOLY
The curve completed 12s after 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.
findingIt left the curve 12s after launch.
noteOnly 2.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 00:55 UTC |
| Creator | 5qaJpvMmDa1Fo2PR9yUR11Ki7HMopA9mycp7KSoLwoaf |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 34 distinct wallets, not counting the creator, bought on the bonding curve: 34 within the first 30s, 7 bundled into the creation block. |
| Graduated | 0 min 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 | not while we watched |
| Recorded from | 2kCdmNkyrevGr9MfwiUpLk… slot 452,454,725
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 00:55:34 UTC Slot 452,454,725, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 00:55:47 UTC +12s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 34 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-10-02 01:02:39 UTC +7m 04s
0.000e+0 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. |
Pool
| Liquidity | 2.3 SOL |
| Read from chain | 2026-10-02 10:42 UTC, just now |
What this launch claimed to be
| Name | ANATWOLY |
| Metadata held | sha256 dd156e471d2d6793c5a65c36eb72636a660a4a38fa662698204939d1f91309a7 · 314 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 cb728db86e2311618df9a518876b83d234ef68ecddcfe50f61273953ef0e4a85 · 602,010 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 00:55 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.