CT
The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
6aK5YeYgnRFwkyyxKL1miHq31oxV251iGv4EHJ6rcDKF
Solscan
not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
findingIt left the curve 0s after launch.
At launch
| Created | 2026-09-30 23:13 UTC |
| Creator | DeH5i5hqRvZLnnZsnX8gnYauCCaP8wMRwjyMVL6FYaSD |
| Creator took | 20.0% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | in the same batch of events as the 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 | 5mPibkXdssCpixdpLjMxxC… slot 452,108,989
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-09-30 23:13:08 UTC Slot 452,108,989, which is the chain's own clock for this moment. |
| Curve completed | 2026-09-30 23:13:08 UTC 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 6 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 141 launches from 116 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 1 earlier launch, 1 confirmed graduated on chain. See the creator's launches → |
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 | Concrete |
| Description | Concrete provides full-stack yield infrastructure for DeFi, powering automated, risk-managed vault products | Backed by |
| Metadata held | sha256 0940af0e9baae111641064bac6049c62a28dac37409f10c20c8f904880ea4211 · 491 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 e5540aa3556ca0e40657b7d9c4eff82d1b82127f3e150b17bf24bf1c0893c9f4 · 1,378 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 23:13 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.