FLOODHAND
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-09-30 23:06 UTC |
| Creator | Bc4FLESWihAdwV5BFSrTSAzjUaeEYsBcMo66EAAQKXW6 |
| 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 | 1 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 | 2SbF6WRAzMehoQRDcWzpJh… slot 452,107,405
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:06:03 UTC Slot 452,107,405, which is the chain's own clock for this moment. |
| Curve completed | 2026-09-30 23:07:07 UTC +1m 04s 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 3 launches from 2 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 6 earlier launches, 4 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 3 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 | FLOODHAND |
| Metadata held | sha256 6324f72540cd277709c9c7f216c681e68192a84ddc4d5726d3cdb1d56f3492ed · 696 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 722af94168b58273bb9733fef359b098bb85bdc290c46de29b7578e3fdfb6d6f · 766 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 23:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.