ESCAP3
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.
At launch
| Created | 2026-10-01 08:58 UTC |
| Creator | Charmy1UtDkndXuv9SaTE2i9WGm2wDwZKyhD7jmo9nsT |
| Creator took | 99.5% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 0 min after launch |
| Curve, read 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 | 5npc2ayBZpvephyY4e7oDa… slot 452,240,444
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-10-01 08:58:09 UTC Slot 452,240,444, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-01 08:58:30 UTC +21s 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 | On 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 3 launches from 3 creator wallets, including this one. See them → |
| This creator | 619 earlier launches, 78 confirmed graduated on chain, 67 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 297 other creator wallets, across 436 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
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 | ESCAP3 |
| Description | ESCAP3 on Meteora DBC |
| Metadata held | sha256 93715942c821c01d9150ce3180edd3b5bb8e7432ab21738c1684c8989c09b94d · 479 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 c2e036dbfa67791dbc5f1bff78c8397756e542102c2c014b23d0d8e0357e7ae0 · 10,483 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 09:00 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.