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 Sui package, `nexus_test_collection_2`, primarily manages `Nft` objects, which are non-fungible tokens with fields for `id`, `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). The `init` function sets up a `Display` object for `Nft`s, a `TransferPolicy` for `Nft`s, and a `TransferPolicyCap`. It configures the `TransferPolicy` to include a `kiosk_lock_rule` and a `royalty_rule` with a 5% royalty. The public functions `mint_order`, `mint_nft`, and `mint_edition_nft` all delegate to a `launchpad` module to handle the actual minting logic, with `mint_edition_nft` also interacting with a `Kiosk`. The `update_nft` function allows a `Manager` to update the `name`, `description`, `media_url`, and `attributes` of an existing `Nft` object within a
This package manages `Nft` objects, which represent non-fungible tokens 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, adding `kiosk_lock_rule` and a `royalty_rule` (5% royalty) to it. All these objects are then transferred or shared. The `mint_order`, `mint_nft`, and `mint_edition_nft` functions are entry points that delegate to a `launchpad` module to handle the minting process of `Nft`s, with `mint_edition_nft` also interacting with a `Kiosk`. The `update_nft` function allows a `Manager` to update the `name`, `description`, `media_url`, and `attributes` of an `Nft` that is held
This package primarily manages `Nft` objects, which represent non-fungible tokens with fields for `name`, `description`, `media_url`, and `attributes` (a `VecMap` of strings). The `init` function initializes the package by creating a `Publisher` object, a `Display` object for `Nft` metadata, and a `TransferPolicy` for `Nft`s with a `kiosk_lock_rule` and a `royalty_rule` set at 5%. These initial objects are then transferred to the transaction sender or shared. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` all delegate to the `launchpad` module to create new `Nft`s, with `mint_edition_nft` also interacting with a `Kiosk`. The `update_nft` function allows a `Manager` to modify the metadata (name, description, media_url, attributes) of an existing `Nft` held within a `Kiosk`. The package uses dynamic fields implicitly through the `Vec
This package defines an Nft object type with fields for ID, name, description, media_url, and attributes. The `init` function initializes a Display object for the Nft type, sets up a TransferPolicy for Nfts with a Kiosk lock rule and a 5% royalty rule (500 basis points), and transfers the Publisher, Display, and TransferPolicyCap objects to the sender, while sharing the TransferPolicy. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` delegate to a `launchpad` module for various NFT minting functionalities, suggesting this package integrates with a broader launchpad system. The `update_nft` function allows modification of an Nft's name, description, media_url, and attributes, requiring a Manager object and Kiosk access. The `create_nft` function is a private helper to construct an Nft object.
This package manages `Nft` objects, which are NFTs with a name, description, media URL, and dynamic attributes. The `init` function initializes the package, creating a `Publisher` object, a `Display` object for `Nft` metadata, and a `TransferPolicy` for `Nft`s with a kiosk lock rule and a 5% royalty rule. Public entry functions include `mint_order`, `mint_nft`, and `mint_edition_nft`, all of which delegate to a `launchpad` module for their core logic, suggesting this module acts as a wrapper or specific implementation for a broader NFT launchpad. The `update_nft` function allows modification of an `Nft`'s metadata fields (name, description, media_url, and attributes) if the NFT is held within a `Kiosk` and the caller possesses the `KioskOwnerCap`. The package utilizes dynamic fields for NFT attributes and implements royalty and kiosk lock rules via `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).
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.
flipperRule-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": "0x8d299b989e3636f97b29059193e61622beb17d70da80caf2ba906bc872ea6600",
"n_tx": 585,
"n_successful_tx": 585,
"n_distinct_epochs": 63,
"n_distinct_sponsors": 0,
"first_seen_cp": 108657898,
"last_seen_cp": 168358743,
"first_seen_ts_ms": 1738605908753,
"last_seen_ts_ms": 1752688273466,
"total_gas_spent_mist": 2720475624,
"n_self_sponsored_tx": 585,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
9,
7,
12,
10,
13,
14,
8,
5,
11,
6,
20,
16,
19,
15,
22,
18,
17,
4,
23,
3,
0,
21,
2
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.7125
],
"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