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 Sui package, `treem`, introduces a new fungible token called TREEM. The `init` function creates the TREEM currency, mints a large initial supply (1,000,000,000,000,000 units) to the transaction sender, and then transfers the `TreasuryCap` (which controls minting/burning) to address `0x0`. The `CoinMetadata` object, containing details like the token's name, symbol, description, and an embedded JPEG image, is then shared publicly. The primary object types managed are `CoinMetadata<TREEM>` and `TreasuryCap<TREEM>`. The package's core logic is to establish a new token, distribute an initial supply, and then effectively disable further minting by transferring the `TreasuryCap` to a burn address (0x0).
This package defines a wrapped SOL (wSOL) token. The primary object types are CoinMetadata<WSOL> and TreasuryCap<WSOL>. The single public/entry function, `init`, creates the wSOL currency, mints an initial supply of 900,000,000,000,000,000 wSOL to the transaction sender, transfers the TreasuryCap to a burn address (0x0), and shares the CoinMetadata object publicly. Notable patterns include the use of `coin::create_currency` to establish a new fungible token, the immediate transfer of the `TreasuryCap` to a burn address, effectively preventing further minting, and the public sharing of the `CoinMetadata` object.
This Sui package, 'my_minter', primarily manages 'Minter' objects, which represent NFT collections, and 'Nft' objects, which are the individual NFTs. Public/entry functions allow the 'Minter' object's owner to add, remove, and update 'SalePhase' configurations, which define pricing, sales limits, and start times for different minting stages. The 'mint' function allows users to mint NFTs, checking against the current sale phase, user-specific mint limits, and an optional Merkle root for allowlist verification. The 'mint' function also handles payment, transferring SUI to the minter's owner. Notable patterns include owner-gating for administrative functions (add_phase, remove_phase, update_phase), time-gating for sale phases, and an optional Merkle tree root for allowlist verification during minting. The 'Minter' object uses dynamic fields (Tables
This Sui package defines an NFT system with custom transfer policies. The primary object types are `Nft` (representing an NFT with metadata like name, description, image, creator, mint number, and rarity) and `Collection` (managing mint supply and minted count for NFTs). The `kiosk_nft` module initializes a `TransferPolicy` for `Nft` objects, adding several rules: `personal_kiosk_rule`, `kiosk_lock_rule`, `royalty_rule`, and `witness_rule`. Public functions allow creating collections, minting NFTs (only by the collection creator and within the mint supply), and updating the mint supply. The `personal_kiosk` module introduces `PersonalKioskCap` to manage `KioskOwnerCap`s, enabling personal kiosks and allowing dynamic field additions to Kiosks to mark them as "personal" and store their owner. The `kiosk_lock_rule` prevents transfers of locked NFTs within a Kiosk, while `personal_kiosk_rule` ensures NFTs are transferred to a personal Kiosk
This Sui package defines a system for managing NFTs and their transfer policies, centered around `Nft` and `Collection` objects. The `kiosk_nft` module allows creators to mint `Nft`s within a `Collection`, with minting restricted to the collection's creator and limited by a `mint_supply`. It also sets up several transfer policies for `Nft`s: `personal_kiosk_rule` ensures NFTs are transferred to a personal kiosk, `kiosk_lock_rule` prevents transfers if the NFT is locked in a kiosk, `royalty_rule` enforces a royalty payment on transfers, and `witness_rule` requires a `Witness` object for transfers. The `personal_kiosk` module introduces `PersonalKioskCap` to manage ownership of Kiosks, allowing a user to "personalize" a Kiosk by setting themselves as the owner via a dynamic field and enabling borrowing/returning of the underlying `KioskOwnerCap`.
botRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
{
"wallet": "0x7682c8538863a72d81f09c1673d50ffda1220d5ec680f7f7f0c527eed0324fac",
"n_tx": 8522,
"n_successful_tx": 8522,
"n_distinct_epochs": 6,
"n_distinct_sponsors": 0,
"first_seen_cp": 277786261,
"last_seen_cp": 282998029,
"first_seen_ts_ms": 1779312655650,
"last_seen_ts_ms": 1780566955781,
"total_gas_spent_mist": 790194256,
"n_self_sponsored_tx": 8522,
"n_sponsored_tx": 0,
"gas_price_p50": 100,
"gas_price_p95": 100,
"active_hours_top24": [
0,
23,
22,
3,
4,
1,
2,
21,
13,
8,
11,
16,
9,
17,
10,
6,
14
],
"primary_archetype": "bot",
"labels": [
"bot"
],
"label_confidence": [
0.9907288
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W. N. America (Pacific/Mountain).