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 new fungible token called "RUNNER". The `init` function, which is called once upon package deployment, creates the `RUNNER` currency by initializing its metadata (name, symbol, description, and icon URL) and minting a `TreasuryCap<RUNNER>`. Both the `CoinMetadata<RUNNER>` and `TreasuryCap<RUNNER>` objects are then transferred to the deployer's address. There are no other public or entry functions, meaning no further minting, burning, or other operations on the `RUNNER` token are directly exposed by this module beyond its initial creation. This module primarily manages the initial setup and distribution of the `RUNNER` token's administrative capabilities.
This package defines a single object type, BURNS, which is a dummy struct. The `init` function is the only public/entry function. It creates a new currency named "BURNS" with a specified symbol, description, and icon URL. It then transfers the `TreasuryCap<BURNS>` and `CoinMetadata<BURNS>` objects to the sender of the transaction. This package essentially sets up a new fungible token called "BURNS" and gives the creator the ability to manage its supply. There are no notable patterns like gating, dynamic fields, or royalties.
This package defines an Nft object with fields for ID, name, description, media_url, and attributes (a VecMap of strings). Most public functions, including minting and updating NFTs, immediately abort, suggesting they are either placeholders or rely on external calls not fully detailed here. The create_nft_with_mutation_request function creates an Nft and an associated NftMutationRequest, while update_nft_with_mutation_request allows modifying an existing Nft's fields (name, description, media_url, attributes) within a Kiosk and generates a mutation request. The package heavily utilizes the 'launchpad' module, likely for managing NFT creation and mutation requests, and interacts with Kiosks for NFT storage.
This Sui package, `theatre`, defines a system for managing NFTs, likely for a theatrical or event-based context. The primary object types are `Manager`, which holds administrative capabilities and manages a collection of `Nft` objects, and `Nft` itself, representing a non-fungible token with attributes like `group_id`, `type`, `name`, `description`, `media_url`, and `attributes`. The public/entry functions are largely stubbed out (aborting with code 2), suggesting an incomplete or placeholder implementation for core functionalities like `withdraw_balance`, `withdraw_reserved_nfts`, `withdraw_royalties`, `add_nft_metadata`, `mint_nft`, and `update_nft`. However, there are two functional public methods: `create_nft_with_mutation_request` creates a new `Nft` object and a corresponding `NftMutationRequest`, and `update_nft_with_mutation_request` modifies an existing `Nft` within a Kiosk and generates an `NftMutationRequest`. Notable patterns
{
"wallet": "0xf76a7e0c6db79ae73b16b24ffb1436770b5f54ea35e404a084eb94c05d4b3d6b",
"n_tx": 2864,
"n_successful_tx": 2844,
"n_distinct_epochs": 248,
"n_distinct_sponsors": 3,
"first_seen_cp": 57794365,
"last_seen_cp": 283482209,
"first_seen_ts_ms": 1726215895175,
"last_seen_ts_ms": 1780674477412,
"total_gas_spent_mist": 10986117852,
"n_self_sponsored_tx": 2638,
"n_sponsored_tx": 226,
"gas_price_p50": 747.8157,
"gas_price_p95": 750,
"active_hours_top24": [
13,
6,
8,
4,
2,
1,
3,
12,
5,
7,
0,
9,
14,
15,
11,
10,
23,
20,
21,
22,
19,
16,
18,
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.