Launch record · observed at creation 2026-11-08 06:12 UTC
NATE
Nate Esparza
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-08 06:12 UTC |
| Creator | 2RenT24wjJF3vvnsBGtofywYXHQ241TrQS4FcEaNYMMo |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown 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. |
| Graduated | 6 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 5mQGLhru5iudHhbepAcuoK… slot 466,809,851
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. 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-08 06:12:21 UTC Slot 466,809,851, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-08 06:17:55 UTC +5m 34s Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
Seen before
| This picture | No other launch we hold a picture for used this one. |
| This ticker | On 148 launches from 111 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 | Nate Esparza |
| Description | NATE |
| Metadata held | sha256 24852a294acb4882b4b2fbabf23e60c708bffd2cf395757b8238e61012aff485 · 300 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 cb1165a27ebb85e0a73ce568b5bcd328a68bf6f2761e13be1d270dfb840fda1b · 377,829 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-08 06:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.