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-11-11 12:10 UTC |
| Creator | 3Cjcr5FqtMbs6imUwYXXhNCKxAbsrixt25d4Sjg6jPu6 |
| Creator took | 0.7% of supply in the first block |
| Outside buyers | 10 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: 10 within the first 30s, 10 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 | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 6.0 h ago and it was finished. Checked 2026-11-11 12:30 UTC. |
| Creator sold | not while we watched |
| Recorded from | AqBSShkSaJzkPdWaCMENXt… slot 468,118,459
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-11 12:10:38 UTC Slot 468,118,459, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-11 12:10:42 UTC +4s Confirmed against the venue's own completion state. |
| Thirty seconds in | 10 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. |
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 | The Muskrat |
| Metadata held | sha256 bb2c6ae7099ffbc6d1f3a4e90e7a70afe5ba3641008c1369a051594b381e0abf · 295 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 3c06420bd627ccd16928c025e6f831e654e17478501f86057b9ce3d185981105 · 220,412 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-11 12:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.