40.0%of supply taken by the creator in the first block
138outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
37launches carry this ticker, from 35 creator walletsThe creator took 40% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
noteThe creator took 40.0% of supply at launch.
At launch
| Created | 2026-11-13 05:01 UTC |
| Creator | 2SkRQLnyWAH5Tk8NX2pieEgB7KFt4p11QpBXv28if5jo |
| Creator took | 40.0% of supply in the first block |
| Outside buyers | 138 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: 11 within the first 30s, 4 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 15 min after launch |
| Curve 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 | 5sWJou3hpCMrS7LE9UK7tM… slot 468,801,831
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-11-13 05:01:22 UTC Slot 468,801,831, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 11 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-11-13 05:16:50 UTC +15m 28s Confirmed: a PumpSwap pool was found for it. |
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 37 launches from 35 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.6% wear one that more than one creator wallet has launched. See this ticker's page → |
Pool
| Liquidity | 56.1 SOL |
| Read from chain | 2026-11-13 10:47 UTC, just now |
What this launch claimed to be
| Name | LocusBot |
| Description | LocusBot is an analytics tool built for memecoin traders. Locus finds calls then sends our users those calls! LIVE NOW |
| Metadata held | sha256 daf4e39d1b64478fd6e03eb70bf9b44b7348f7c3efffeedd59a99d69e29dad4f · 445 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 a2bd4ad0e889a6d68af4e01d3889490967f1d8cea97490d5f4393c62e3241649 · 866,838 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-13 05:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.