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.
This package defines a new fungible token, NTC (Nautical), with a fixed supply of 6 units. The `init` function, which runs once on package deployment, creates the `CoinMetadata<NTC>` and `TreasuryCap<NTC>` objects for this new token. These objects are then immediately transferred to the deployer's address. There are no other public or entry functions, meaning users cannot mint, burn, or interact with the NTC token beyond its initial creation and transfer. The package does not manage any other primary object types, nor does it exhibit any notable patterns like signature/allowlist gating, time-gating, dynamic fields, or vault/escrow functionalities.
This package defines a single primary object type, NTC, which is a dummy struct. The init function, which is called once upon package deployment, creates a new fungible token (Coin) of type NTC. It initializes the token's metadata including its symbol ("NTC"), name ("Nautical Space"), description, and a URL for its image. The TreasuryCap and CoinMetadata objects for this new token are then publicly transferred to the deployer of the package. There are no other public or entry functions, meaning no further token operations are directly exposed by this module. The package essentially deploys a new token and grants its management capabilities to the deployer.
This package defines a single object type, `SPC`, which is a dummy struct used as a phantom type parameter. The `init` function is the only public/entry function. It creates a new `CoinMetadata<SPC>` object and a `TreasuryCap<SPC>` object, effectively defining a new fungible token named "SPC" with a specific symbol, description, and icon URL. Both the `TreasuryCap` and `CoinMetadata` objects are then transferred to the sender of the transaction. This module primarily focuses on the initial setup and distribution of a new token, with no further token management or interaction logic.
This Sui package defines a single module, `tako`, which manages a custom coin type also named `TAKO`. The primary object types are `TAKO` (a dummy struct), `CoinMetadata<TAKO>`, and `TreasuryCap<TAKO>`. The `init` function is the only public/entry function, and it initializes the `TAKO` coin, setting its metadata (name, symbol, description, icon URL) and freezing the `CoinMetadata` object. It then transfers the `TreasuryCap` for the `TAKO` coin to the deployer of the module. This package exhibits a common pattern for creating new fungible tokens on Sui, where the `TreasuryCap` grants minting authority.
nft_collectorRule-based labels, conservative precision.
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": "0x183f54bded69ecdc5ef6a2bb8efbe96aa0719c1b191da843d52431269ed76c87",
"n_tx": 11212,
"n_successful_tx": 11024,
"n_distinct_epochs": 351,
"n_distinct_sponsors": 3,
"first_seen_cp": 71747951,
"last_seen_cp": 282558714,
"first_seen_ts_ms": 1729621638297,
"last_seen_ts_ms": 1780469742889,
"total_gas_spent_mist": 80703061924,
"n_self_sponsored_tx": 11176,
"n_sponsored_tx": 36,
"gas_price_p50": 710.7807,
"gas_price_p95": 741,
"active_hours_top24": [
12,
15,
8,
3,
11,
1,
0,
23,
5,
13,
10,
22,
14,
2,
9,
4,
7,
6,
16,
17,
21,
20,
19,
18
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector"
],
"label_confidence": [
0.705
],
"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