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.
This package manages a primary object type called `Nft`, which represents a non-fungible token with fields for ID, name, description, media URL, and attributes (a `VecMap` of strings). The `init` function initializes the module by creating a `Publisher` object, a `Display` object for `Nft`s with predefined metadata fields, and a `TransferPolicy` for `Nft`s. This `TransferPolicy` includes a `kiosk_lock_rule` and a `royalty_rule` set to 3% (300 basis points). All these objects (Publisher, Display, TransferPolicyCap) are transferred to the sender, and the TransferPolicy is shared. The `create_nft_with_mutation_request` function creates a new `Nft` object and a corresponding `NftMutationRequest`, which is likely used for off-chain or deferred updates. The `update_nft_with_mutation_request` function allows modification of an existing `Nft`'s fields (name, description, media_url, attributes)
This package defines a commission system centered around the `Manager` object. The `Manager` object, controlled by an `admin` address, oversees the creation and management of `RewardManager` objects. `RewardManager` objects define reward rates and track NFT registrations for reward distribution. Public functions allow the admin to set the manager's version and admin address, and to add or update `RewardManager` configurations. Users can `pay` into the system, which deposits funds into the manager's balance and potentially allocates a portion as rewards to a specific `RewardManager`. Users can also `pay_reward` or `withdraw_reward` for their NFTs, which transfers accumulated rewards from a `Reward` object (associated with a `RewardManager`) to their Kiosk. The `withdraw` function allows the admin to extract funds from the manager's balance. The system utilizes dynamic fields to store balances for different coin types and `RewardManager` objects, and linked tables to track NFT registrations and individual reward payouts.
This package defines an `Nft` object type with fields for ID, name, description, media URL, and attributes (as a VecMap). The `init` function creates a `Publisher` object, a `Display` object for `Nft`s, and a `TransferPolicy` for `Nft`s, which includes a kiosk lock rule and a 5% royalty rule. All public/entry functions (`mint_order`, `mint_nft`, `mint_edition_nft`, `update_nft`) immediately abort with an error code of 1, indicating they are not yet implemented or are placeholders. The `init` function transfers ownership of the `Publisher`, `Display`, and `TransferPolicyCap` to the transaction sender, and shares the `TransferPolicy` object. Notable patterns include the use of `Display` for metadata, `TransferPolicy` for transfer rules (kiosk lock, royalties), and the presence of unimplemented public functions.
This package manages `Nft` objects, which are NFTs with a name, description, media URL, and dynamic attributes stored as a `VecMap<String, String>`. The `init` function initializes a `Display` object for `Nft`s, sets up a `TransferPolicy<Nft>` with a `kiosk_lock_rule` and a `royalty_rule` (with 0% royalty), and then shares the `TransferPolicy` while transferring the `Publisher`, `Display`, and `TransferPolicyCap` to the transaction sender. The `mint_order`, `mint_nft`, and `mint_edition_nft` public functions delegate to the `launchpad` module to handle the actual minting logic, creating `Nft` objects internally and passing them to the `launchpad`. The `update_nft` function allows a `Manager` to update the name, description, media URL, and attributes of an `Nft` object that is held within a Kiosk.
This Sui package primarily manages `Nft` objects, which represent non-fungible tokens with fields for name, description, media URL, and a dynamic map of attributes. The `init` function sets up a `Display` object for `Nft`s, a `TransferPolicy` with a kiosk lock rule and a 0% royalty rule, and transfers the `Publisher`, `Display`, and `TransferPolicyCap` to the deployer, while sharing the `TransferPolicy` object. Public functions include `mint_order`, `mint_nft`, and `mint_edition_nft`, which delegate to a `launchpad` module to create new `Nft`s, and `update_nft` which modifies the name, description, media URL, and attributes of an existing `Nft` within a Kiosk. The package utilizes dynamic fields for NFT attributes and implements royalty and kiosk lock rules via the `TransferPolicy`.
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
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": "0xc92c43d4c998098dd4b0953a17d4625678b11a2e82e22d9d278c11776da5653b",
"n_tx": 218,
"n_successful_tx": 208,
"n_distinct_epochs": 47,
"n_distinct_sponsors": 0,
"first_seen_cp": 154881257,
"last_seen_cp": 280307908,
"first_seen_ts_ms": 1749494728033,
"last_seen_ts_ms": 1779889346864,
"total_gas_spent_mist": 1176179472,
"n_self_sponsored_tx": 218,
"n_sponsored_tx": 0,
"gas_price_p50": 549,
"gas_price_p95": 711,
"active_hours_top24": [
15,
12,
13,
10,
14,
8,
6,
11,
9,
16,
17,
23,
18,
7,
22,
20,
0,
2,
19
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0.5,
"bot_signals": [
"wash_trader"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail