← all tokens
KOLs Coin KOLs
B2uyUxeq7mzh8hvHhdeGeo9DXpGMi1Fhmy2CGgrZpump
The mintslot 451,453,584
token programTokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
supply1000000000000000
decimals6
mint authoritynull: revoked
freeze authoritynull: revoked
Fee configurationslot 451,453,584
0.0080 SOLPENDING
8,017,920 lamports · read at slot 451,453,584
Held by the configuration account. It is addressed to nobody and nobody has taken it, so it is not claimable and certainly not received.
config accountGnfuzu6djPNoPCCiyQTbAVgYkzrSeQtHeHQ2ZTCsCQE3
adminCAqEXGUj6ZhDejjUTieX2QxU9pbWW5P4vXBo7c4QveSB
byte 751: shown, not interpreted
shareholders9
holder 0suqh…HQfK · 12.00% (1200 bps)
holder 14sAU…m5nU · 11.00% (1100 bps)
holder 24vw5…9Ud9 · 11.00% (1100 bps)
holder 3831y…eoEs · 11.00% (1100 bps)
holder 489Hb…mkDi · 11.00% (1100 bps)
holder 58MaV…88D5 · 11.00% (1100 bps)
holder 6BAr5…XJPh · 11.00% (1100 bps)
holder 7BCag…UPJd · 11.00% (1100 bps)
holder 8CyaE…a54o · 11.00% (1100 bps)
shares add up to10000 bps: the whole fee
These were printed as raw bytes until 2026-09-22, with a note saying the share reading was wrong: they read 10000 in 3,874 of 3,880 single-holder configs, yet 0 of 120 multi-holder configs summed to 10000. The control was right to stop the claim and wrong about why. The field was always basis points. The stride was wrong. An entry is 34 bytes, not 40, so every holder after the first was being read six bytes inside the previous one’s share. Re-read at 34, 24 of 24 multi-holder configs sum to exactly 10000.