Launch record · observed at creation 2026-11-10 12:29 UTC
CABAL
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-10 12:29 UTC |
| Creator | EN2ZscbT7qZV7qa2hebqgJrifMfgfFkMLfPMoMUSnF2k |
| 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 | 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 recorded - this venue's trades do not name the wallet |
| Recorded from | 3pKYHHqv9eJohf3TaKcQDC… slot 467,720,892
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.
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-10 12:29:35 UTC Slot 467,720,892, which is the chain's own clock for this moment. |
| Highest price seen | 2026-11-10 12:29:35 UTC +0s
0.000e+0 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 205 launches from 164 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 | CABAL |
| Description | The cabal is real. It’s just 1 dev sitting in a room with 4 monitors, drinking energy drinks and pus |
| Metadata held | sha256 773169e44e3fbdeba70404dce1ae573b8d5744a835f949c4b2f138bb4c7ff5da · 423 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 a809650f1407be1df92e82c52d92a68a4a757df4dc1a15d1d54c7d37cf344e61 · 65,924 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 12:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.