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 `GEMS` object, which is a dummy struct used as a type parameter for a new fungible token. The `init` function, which runs once on package deployment, creates a new `GEMS` currency, its associated `CoinMetadata`, `TreasuryCap`, `TokenPolicy`, and `TokenPolicyCap`. It then shares the `CoinMetadata` publicly, transfers the `TreasuryCap` and `TokenPolicyCap` to the deployer, and shares the `TokenPolicy` publicly. This establishes the infrastructure for a new fungible token named "GEMS" with the description "Accumulate Gems to unlock rewards in the DSL ecosystem." The primary objects managed are `CoinMetadata<GEMS>`, `TreasuryCap<GEMS>`, `TokenPolicy<GEMS>`, and `TokenPolicyCap<GEMS>`. The notable pattern is the creation and distribution of these core token-related objects during initialization, with the `TreasuryCap` and `TokenPolicyCap` being transferred to the deployer for administrative control.
This package manages "RollifyTicket" objects, which are NFTs with a unique ID, number, image URL, and custom attributes. It also manages "Whitelist" objects, which track addresses eligible for airdrops and whether they've received one, and "Supply" objects, which track the total minted tickets and a maximum supply. An "AdminCap" object grants administrative privileges. Public functions allow administrators to add or remove addresses from a whitelist, airdrop single or batch tickets to whitelisted addresses (mutating the Whitelist and Supply objects), and create new AdminCaps. Users can burn their RollifyTickets. Notable patterns include the use of an AdminCap for gating administrative functions, a whitelist for controlled distribution, and events emitted for airdrops and burns.
This package implements a coin-flip game with administrative controls and partnership features. The primary object types are `AccessControl` (managing roles and permissions) and `House` (managing the game's funds and parameters). Public/entry functions allow users to `flip` a coin (single or multiple times) with or without a `Partnership` object, which can reduce fees or require a `Kiosk` item for participation. These functions mutate the `House` object by transferring funds (Coins) to or from it based on game outcomes and fees. Notable patterns include signature/allowlist gating through the `AccessControl` object, which uses `VecMap` and `VecSet` to manage roles and addresses, and the use of dynamic fields for `Partnership` objects. The `Admin` object acts as an admin cap, granting specific roles to addresses.
This package defines a Decimal type for fixed-point arithmetic and a VestingManager object to handle token vesting. The Decimal module provides functions for creating, converting, and performing arithmetic operations on Decimal values, which internally store a u256. The mtoken module's VestingManager manages the vesting of a generic token (Ty0) by holding a TreasuryCap for minting, a balance of the vested token (Ty1), and a balance for penalties (Ty2). Public/entry functions allow an AdminCap holder to mint new mtokens, set vesting parameters (penalty numerators, denominator, start/end times), and collect accumulated penalties. The redeem_mtokens function allows users to burn mtokens (Ty0) and receive vested tokens (Ty1), with a penalty (Ty2) applied based on the vesting schedule and current time, which is then transferred to the penalty_balance. The AdminCap acts as an allowlist for administrative actions, and the vesting schedule is time-gated.
This package defines a single module `mwin_series_1` that manages a custom coin type, `MWIN_SERIES_1`. The `init` function is the only public/entry function, which creates and initializes this new coin. It mints a `TreasuryCap` for `MWIN_SERIES_1` and transfers it to the transaction sender, while also sharing the `CoinMetadata` object publicly. The coin's metadata includes its name ("mWIN Series 1"), symbol ("mWIN"), decimals (9), and an icon URL ("https://winx.io/mWIN.svg"). This module essentially sets up a new fungible token on Sui.
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": "0xd37e298017b8970fb775664edeb996d940ab7caf85d94e9bc206d585ec4b6a44",
"n_tx": 2701,
"n_successful_tx": 2488,
"n_distinct_epochs": 148,
"n_distinct_sponsors": 0,
"first_seen_cp": 50274059,
"last_seen_cp": 244426861,
"first_seen_ts_ms": 1724383654461,
"last_seen_ts_ms": 1770950550383,
"total_gas_spent_mist": 56616737736,
"n_self_sponsored_tx": 2701,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 754,
"active_hours_top24": [
6,
7,
5,
4,
8,
2,
3,
0,
9,
15,
1,
11,
12,
10,
23,
16,
14,
13,
22,
20,
17
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. Asia / Oceania.
area + brightness = call volume; hover for detail