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 manages two primary object types: `Claim` and `PreSale`. The `Claim` object facilitates token claims with a start/end time, an emergency switch, and two `Bag` dynamic fields (`claim_members` and `unclaim_members`) to track member claim statuses and amounts. The `PreSale` object manages token presales, featuring a whitelist, start/end times, min/max investment amounts, and `Bag` dynamic fields (`white_listed` and `members`) for tracking whitelisted addresses and participant contributions. Both objects are managed by an associated capability object (`ManageCap` for `Claim` and `ManageCapAbility` for `PreSale`), which gates administrative functions like changing end times, adding/removing whitelist members, and emergency operations. Funds are held in a `Coin` balance within both `Claim` and `PreSale` objects, and events are emitted for claim and sale activities.
This package manages a generic `NonTransferCoin` object, which wraps a `balance::Balance` and stores an `owner` address. Public functions allow querying the coin's value and owner, and borrowing its internal balance. Coins can be created from a zero balance or an existing balance, and their internal balance can be extracted. Multiple `NonTransferCoin` objects can be combined using `join` or `join_vec`, and a single coin can be split into a new `NonTransferCoin` object using `split`, `split_vec`, or `split_and_keep`. The `keep` function transfers a `NonTransferCoin` to the transaction sender, and `destroy_zero_or_transfer` either destroys a zero-value coin or transfers it to the sender. The `NonTransferCoin` object is designed to be non-transferable directly, as indicated by its name and the use of `transfer::public_transfer` only to the transaction sender.
This package defines a single object type, LLP, which is a dummy struct. The `init` function is the only public/entry point and is responsible for creating a new coin type named "LLP". It mints 1.5 billion units of this coin and transfers both the `TreasuryCap<LLP>` and the minted `Coin<LLP>` to the sender of the transaction. The `CoinMetadata<LLP>` is frozen. This module essentially initializes a new fungible token with a fixed initial supply, and the `TreasuryCap` allows for future minting.
This package introduces a claim mechanism for a generic token type (Ty0) and a specific token called XLUCK. The primary objects are `Claim<Ty0>`, which manages token distributions, and `ManageCap<Ty0>`, an administrative capability for a specific claim. The `xLuck` module defines the `XLUCK` token and a `MintAbility<XLUCK>` object that controls its supply. Public functions allow creating a claim, changing its end time, and users can claim their allocated tokens within a specified time window. Administrators can add members to a claim list, toggle an emergency switch, and perform emergency deposits/withdrawals of tokens from a claim. The `MintAbility` object is used to mint new XLUCK tokens and transfer them to a recipient.
This package manages LuckyNFT objects, which have a name, image URL, level, and points. The `init` function initializes a TransferPolicy for LuckyNFTs, adding a rule that charges a fee (5% or 1000 units, whichever is higher) on transfers, and creates MintCap and BurnCap objects, transferring them to the deployer. Public functions allow users holding a MintCap to mint new LuckyNFTs to themselves or another address, and users holding a BurnCap to burn LuckyNFTs. A `MintState` object can be created and shared to enable public minting, which can be toggled on/off. Public minting is restricted to one NFT per sender. LuckyNFTs can have their points increased, which also updates their image URL and level based on point thresholds. The `rule` module defines a configurable fee rule for transfer policies, charging a percentage or minimum amount.
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": "0xb3fdd98fe7cc8fc8a20310cf96be44245b6d0204319ace77763fcd09689c42e7",
"n_tx": 360,
"n_successful_tx": 339,
"n_distinct_epochs": 55,
"n_distinct_sponsors": 0,
"first_seen_cp": 1800263,
"last_seen_cp": 30317940,
"first_seen_ts_ms": 1683356073127,
"last_seen_ts_ms": 1711989129266,
"total_gas_spent_mist": 55551162424,
"n_self_sponsored_tx": 360,
"n_sponsored_tx": 0,
"gas_price_p50": 887,
"gas_price_p95": 1000,
"active_hours_top24": [
10,
6,
9,
14,
7,
15,
3,
5,
13,
8,
2,
11,
12,
1,
4,
16
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely E. / SE Asia.
area + brightness = call volume; hover for detail