USDT
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
9SLtoB4DAXh6Cg282oRBJqvbqyBvvvvHbUREwGPPuWqY
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.
At launch
| Created | 2026-09-30 01:37 UTC |
| Creator | 47h1bE5tGy9FtV4nxRYNZj611hD1pK6wdmQPDN6H38sw |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 3 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 | 3nYeyTYR7UiQ1ZMf8RB6BA… slot 451,818,507
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 01:37:47 UTC Slot 451,818,507, which is the chain's own clock for this moment. |
| Curve completed | 2026-09-30 01:40:59 UTC +3m 12s 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 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 146 launches from 104 creator wallets, including this one. See them → |
| This creator | 4 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. 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 | usdt |
| Description | usdt — launched on DBC Forge |
| Metadata held | sha256 8a92ca30424f5b46c7825d448e10337002d904c4c3b39dba2d5d8ff28fcbab04 · 230 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 c94dd3b5d4b2d110ff762aa3f90ac6270a2d9544cba64b11a5937b3ba431ed62 · 9,971 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 22:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.