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 an NFT collection for "BirdNFT" objects. The primary object types are `BirdNFT` (the NFT itself), `AdminCap` (for administrative control), `Register` (to track minting nonces), `BirdConfig` (global configuration for the NFT collection and fees), and `SaleConfig` (for managing NFT sales rounds). Public/entry functions allow users to `buy` BirdNFTs during public or private sale rounds, provided they meet whitelist and time-gating conditions, and `mint` BirdNFTs using a signed message from a validator and a nonce system. Both `buy` and `mint` functions transfer SUI fees to the `BirdConfig` object's `fee_balance`. Users can also `burn` their BirdNFTs. Notable patterns include: an `AdminCap` for privileged operations, a `Register` object that uses a `Table` to track user nonces for minting, `BirdConfig` which holds a `Balance<SUI>` for collected fees and an optional `validator` public key
This package manages "Campaign" objects, which represent reward campaigns, and "RewardPool" objects, which hold the actual rewards. An "AdminCap" object grants administrative privileges. Public functions allow administrators to create new campaigns and reward pools, update campaign parameters like total and individual rewards, and pause/unpause the entire system or specific campaigns. The `claim` function enables whitelisted users to claim their rewards from a campaign's reward pool, provided the campaign is active and within its time limits. Notable patterns include: an "AdminCap" for access control, time-gating for campaign start and end times, and dynamic fields (implemented via `table`s) to store campaign-specific data like whitelisted users, claimed status, and reward amounts per pool. The `Config` object acts as a singleton for global settings, and events are emitted for significant actions like campaign creation, reward pool creation, and reward claims.
This package defines an NFT collection for "BirdNFT" objects. It includes an AdminCap for administrative actions and a UserArchive to track user minting activity. Users can mint BirdNFTs through two public functions: 'buy' for a public/private sale with whitelisting and time-gating, and 'mint' which requires a signed message for specific parameters and a nonce check. Both minting functions accept SUI coins as payment, which are collected into a fee_balance within the BirdConfig object. The package also allows for burning BirdNFTs and includes administrative functions to configure sale types, update sale times, manage whitelists, and set bird type parameters.
This Sui package manages "UserArchive" objects, which store information about a user's deposited "BirdNFT" (Non-Fungible Token) and their in-game activities. Users can register their BirdNFTs, initiating various game mechanics like daily check-ins, preying, and mating. The public/entry functions allow users to register a bird, retrieve archive data, and validate various states related to their bird and activities. The package uses dynamic fields (Table) to store nonce values and a registry of registered users. Time-gating is implemented for check-ins, preying, and claiming rewards, and there are checks to ensure birds are not actively preying or mating when certain actions are attempted.
This Sui package primarily manages `UserArchive` objects, which store detailed information about a user's NFT birds, including their type, check-in data, mission rewards, preying status, energy, and mating details. Public/entry functions allow users to register their birds, which creates a `UserArchive` object and records the bird's initial state, and retrieve archive data. Notable patterns include the use of dynamic fields within `UserArchive` (e.g., `nonce_type` as a `Table<u8, u128>`) and time-gating mechanisms for actions like bird withdrawal and claiming rewards (e.g., `withdrawal_time`, `claiming_time`). The `Reg` object acts as an allowlist or registry for addresses that have registered birds.
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.
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": "0xe74e9130d9b761068b00e89260230c4a1e9f3cc5d977edce1000d1da3c1f6609",
"n_tx": 1328,
"n_successful_tx": 1216,
"n_distinct_epochs": 62,
"n_distinct_sponsors": 0,
"first_seen_cp": 98519400,
"last_seen_cp": 236118033,
"first_seen_ts_ms": 1736152362095,
"last_seen_ts_ms": 1768811963460,
"total_gas_spent_mist": 17207538172,
"n_self_sponsored_tx": 1328,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
10,
9,
8,
7,
3,
14,
2,
1,
0,
11,
6,
4,
22,
5,
12,
15,
23,
13,
18,
16,
21,
20
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"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 E. / SE Asia.
area + brightness = call volume; hover for detail