QUANT
The curve completed 1s after 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.
findingIt left the curve 1s after launch.
noteOnly 8.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 16:54 UTC |
| Creator | DvrH45izrUQHCCpvMBUBz4KAZFWU6sDc5wKNE3cyGm2P |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 23 distinct wallets, not counting the creator, bought on the bonding curve: 23 within the first 30s, 18 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 64ENW26RwJ82o8EhwTEzD1… slot 452,669,960
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 16:54:24 UTC Slot 452,669,960, which is the chain's own clock for this moment. |
| Creation block | 18 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 16:54:25 UTC +1s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 16:54:25 UTC +1s
4.109e-7 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. |
| Thirty seconds in | 23 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 | On 18 launches from 18 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 210 launches from 166 creator wallets, including this one. See them → |
Pool
| Liquidity | 8.7 SOL |
| Read from chain | 2026-10-02 20:06 UTC, just now |
What this launch claimed to be
| Name | Quants.bid |
| Description | the official house token for the quants.bid platform |
| Metadata held | sha256 08b91fdb8aedbcd9f66eb9ba9d12896f44014c14b07edde433f157b1bf8602dd · 315 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 a517efcd81df7e77edc00fb6b51fb0410be3e5ea56ab763a8d106107cc145eb3 · 5,791 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 16:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.