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 single primary object type, NYC, which is a dummy struct. The `init` function is an entry function that creates a new fungible token (Coin) named "NYC" (New York City) with a specified description and IPFS image URL. It then transfers the `TreasuryCap<NYC>` and `CoinMetadata<NYC>` objects to the sender of the transaction. The package does not manage any other objects or have other public/entry functions. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties.
This Sui package defines a single module, 'vul', which primarily manages a custom coin type called 'VUL'. The 'init' function, which is an entry point, creates and initializes this 'VUL' coin. It sets up the coin's metadata, including its symbol ("VUL"), name ("Vulcano"), description ("Dangerous"), and an image URL. Finally, it transfers the newly created TreasuryCap and CoinMetadata objects for the 'VUL' coin to the deployer of the module. This module essentially acts as a coin factory, with no other public functions for further interaction or mutation of the coin or other objects.
This package defines a single object type, `LTM`, which is a dummy struct. The `init` function creates a new fungible token called "LATOM" (LTM) with a supply of 6, a description "Fire on the world", and a specific IPFS URL for its icon. It then transfers the `TreasuryCap<LTM>` and `CoinMetadata<LTM>` objects to the sender of the transaction. This module primarily focuses on the initial setup and distribution of a new fungible token, with the `TreasuryCap` enabling future minting/burning and the `CoinMetadata` providing token details.
This package defines a single object type, `TRAIN`, which is a dummy struct. The `init` function is a one-time initializer that creates a new fungible token (Coin) named "TRAIN" with a specified symbol, name, description, and an IPFS URL for its icon. It then transfers the `TreasuryCap<TRAIN>` and `CoinMetadata<TRAIN>` objects to the sender of the transaction. This pattern indicates the creation of a new custom coin and the transfer of its administrative capabilities and metadata to the deployer.
This package defines a new fungible token called "NOT". The primary objects it manages are the `TreasuryCap<NOT>` and `CoinMetadata<NOT>` for this token. The `init` function is the only public/entry function, and it creates the `NOT` currency with a supply of 6, a description, and a URL. It then transfers both the `TreasuryCap<NOT>` and `CoinMetadata<NOT>` to the sender of the transaction. There are no other notable patterns like signature gating, time-gating, dynamic fields, or vault/escrow functionality.
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.
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": "0x517bedff0408fb7d44891b2d05a5b142cc852a3e545b47fd6fc4b012332028a4",
"n_tx": 2824,
"n_successful_tx": 2749,
"n_distinct_epochs": 126,
"n_distinct_sponsors": 0,
"first_seen_cp": 70211443,
"last_seen_cp": 191226374,
"first_seen_ts_ms": 1729242964704,
"last_seen_ts_ms": 1758186875311,
"total_gas_spent_mist": 5558621604,
"n_self_sponsored_tx": 2824,
"n_sponsored_tx": 0,
"gas_price_p50": 753.6964,
"gas_price_p95": 825,
"active_hours_top24": [
10,
15,
7,
8,
14,
11,
9,
16,
13,
4,
5,
3,
2,
12,
6,
17,
18,
1,
0,
22,
23,
20,
19,
21
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail