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 23:21 UTC |
| Creator | 5P12RkKTsKcM8D9E4YDtcVc8dcwEY3XrYTo9a2QF7TLo |
| Creator took | 20.1% of supply in the first block |
| Outside buyers | 64 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: 15 within the first 30s, 9 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 | 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 | not while we watched |
| Recorded from | 52jyV1H8RBi5kFaagK49u6… slot 443,821,031
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 23:21:00 UTC Slot 443,821,031, which is the chain's own clock for this moment. |
| Creation block | 9 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-02 23:21:00 UTC
3.306e-7 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. |
| Thirty seconds in | 15 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. |
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 940 launches from 772 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 | ArtificialLlama |
| Description | Meta built Llama. The internet gave it a personality. 🦙 Artificial Llama, paired with tokenized $META. |
| Metadata held | sha256 14e340f03d3825fd4c7dc0a27254b5ac34e0c9b94b2bc5a4d81f63ef2a3cdeeb · 534 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 10b38923f038557c2a17fa5f9442419bfa7248d4df2f091e13b8a42ed0b5ffc3 · 37,272 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-11 01:05 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.