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 system for managing administrative capabilities and system configuration. It primarily manages three object types: AdminCap, ModeratorCap, and SystemConfig. The init function creates an AdminCap and transfers it to the deployer, and also creates and shares a SystemConfig object with initial values. Public functions allow an AdminCap holder to create new ModeratorCaps, update the max_users field in the shared SystemConfig, and toggle the maintenance_mode in the SystemConfig. A ModeratorCap holder can call moderate_content, which returns true if the provided u64 is greater than 0, but this function does not mutate any objects. A notable pattern is the use of capability-based access control, where AdminCap and ModeratorCap objects gate access to specific functionalities.
This package manages a single primary object type: `UserProfile`. The `create_profile` entry function creates a new `UserProfile` object with a name, age, email, and creation timestamp, then transfers it to the transaction sender and emits a `ProfileCreated` event. The `update_age` public function allows modifying the `age` field of an existing `UserProfile` object. The `get_name`, `get_age`, and `get_email` public functions are read-only and retrieve the respective fields from a `UserProfile` object. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties.
This package manages a single primary object type, `Greeting`, which stores a unique ID and a string message. The `create_greeting` public entry function allows anyone to create a new `Greeting` object with a specified message (as a UTF-8 byte vector) and shares it globally, making it accessible to all. The `get_message` public function allows anyone to retrieve the message string from an existing `Greeting` object without mutating it. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties present in this module.
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.
area + brightness = call volume; hover for detail
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": "0x5916b4d498dea5dce22db65ccd81a1b6194b64c6269a974c403782140c91a9ca",
"n_tx": 130,
"n_successful_tx": 127,
"n_distinct_epochs": 23,
"n_distinct_sponsors": 0,
"first_seen_cp": 152825722,
"last_seen_cp": 183626239,
"first_seen_ts_ms": 1749006738854,
"last_seen_ts_ms": 1756347887657,
"total_gas_spent_mist": 1108229564,
"n_self_sponsored_tx": 130,
"n_sponsored_tx": 0,
"gas_price_p50": 741,
"gas_price_p95": 742,
"active_hours_top24": [
8,
7,
9,
6,
2,
12,
3,
11,
10,
4,
13,
5
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.