all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
The `labbo` package introduces a new fungible token called `LABBO`. The `init` function creates this currency, mints a large initial supply (8,888,888,888,888,888,888 units) to the deployer, and then transfers the `TreasuryCap<LABBO>` to a hardcoded address (0x00...). The `CoinMetadata<LABBO>` object is then shared publicly. The primary object types managed are `CoinMetadata<LABBO>` and `TreasuryCap<LABBO>`. The public/entry functions are limited to the `init` function, which initializes the token and distributes its `TreasuryCap`. A notable pattern is the hardcoded transfer of the `TreasuryCap` to a specific address, indicating a potential administrative or vault-like control over the token's minting capabilities.
This Sui package, "nightmare", primarily manages a custom fungible token called "NIGHTMARE". The package has a single public/entry function, `init`, which is called only once during package deployment. This `init` function creates the `NIGHTMARE` token's `CoinMetadata` and a `TreasuryCap`. It then mints a large quantity of `NIGHTMARE` tokens (1,313,131,313 tokens) and immediately transfers them to the deployer's address. Finally, it transfers the `TreasuryCap` to address `0x0` (effectively burning it) and shares the `CoinMetadata` object publicly. This means no more `NIGHTMARE` tokens can be minted after initialization, and the token's metadata is publicly accessible.
This Sui package defines a single primary object type, `LAZY_SLOTH`, which is a dummy struct. The package has one public entry function, `init`, which is called once during package deployment. This `init` function creates a new fungible token (coin) of type `LAZY_SLOTH`, mints a large initial supply (999,999,999,900,000,000 units) of this coin, and transfers all of it to the deployer's address. It then transfers the `TreasuryCap<LAZY_SLOTH>` object to a zero address (effectively burning it or making it inaccessible for further minting), and shares the `CoinMetadata<LAZY_SLOTH>` object publicly. The package establishes a new fungible token with a fixed supply and makes its metadata publicly available, while preventing further minting by transferring the `TreasuryCap` to a non-recoverable address.
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Tinted amber on the bubble map when they appear in the expanded graph.
Where this wallet's SUI first came from, and what it seeded downstream. Observational: a CEX funder suggests a real/retail origin; a high-fanout non-CEX funder is a signal worth noting — not proof of anything.
{
"wallet": "0x85624a42cb13f8d815bffcdc0292c33524cbb28e1ffe8e6a29ff616b08f88cb7",
"n_tx": 449,
"n_successful_tx": 444,
"n_distinct_epochs": 39,
"n_distinct_sponsors": 0,
"first_seen_cp": 35989150,
"last_seen_cp": 88832689,
"first_seen_ts_ms": 1717655559741,
"last_seen_ts_ms": 1733805773296,
"total_gas_spent_mist": 3580047564,
"n_self_sponsored_tx": 449,
"n_sponsored_tx": 0,
"gas_price_p50": 758,
"gas_price_p95": 759,
"active_hours_top24": [
17,
15,
8,
2,
6,
7,
14,
5,
4,
16,
18,
19,
0,
3,
11,
20,
12,
10,
21,
9,
1,
13
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail