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 package manages a single primary object type called `Big`, which contains a UID and 31 `u64` fields (f1 through f31). The `init` function is the only public/entry function. It creates a new `Big` object, initializes all its `u64` fields to 0, and then shares this `Big` object, making it globally accessible. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties present in this module.
This Sui package, bubble_draw, implements a lottery-like game where users buy "bubbles" to participate in draws. The primary object type is BubbleDraw<Ty0>, which holds game state, participant data, and various SUI and generic coin balances for pools and rewards. Public entry functions allow users to buy bubbles, set a referrer, and claim rewards. The contract features a referral system where referrers earn a percentage of referred purchases, and a pass system that provides multipliers for earned rewards. There are also admin-gated functions for creating the draw and withdrawing treasury funds, and time-gating for draw participation and winner selection. The contract uses dynamic fields (Table) to store participant passes, referral information, and pop claims.
This package primarily manages a `RandomGenerator` object type. The single public entry function, `test_random`, takes a shared `Random` object and a mutable `TxContext` as input. It initializes a new `RandomGenerator` using these inputs, then uses this generator to produce a random `u64` value within the range [0, 100) but does not store or return this value. The function's primary purpose appears to be demonstrating the use of the `random` module to generate a random number.
This package defines a staking pool for liquidity provider (LP) tokens, allowing users to stake LP positions and earn rewards in three different token types (Ty0, Ty1, Ty2). The primary object managed is the `StakingPool`, which holds reward balances, staking rates, and dynamic tables for `StakedPosition` objects and player stakes. The `init` function creates an `AdminCap` and transfers it to the deployer, granting administrative control. Public/entry functions include `create_pool` (admin-gated) to initialize a new staking pool, `top_up_a/b/c` (admin-gated) to add rewards of specific token types to the pool, and `emergency_withdraw` (admin-gated) to withdraw all remaining rewards from the pool. Notable patterns include admin-gating for critical pool management functions, time-gating through `clock::timestamp_ms` for reward rate calculations, and the use of dynamic tables (`staked_positions` and `player_stakes`) to manage individual staked
This package manages `StakingPool` objects, which are generic over three reward token types. An `AdminCap` is required for administrative functions. The `init` function creates and transfers an `AdminCap` to the deployer. Administrative functions like `create_pool`, `fund_rewards_a/b/c`, `withdraw_rewards_a/b/c`, `set_emissions`, and `set_paused` are gated by this `AdminCap`. `create_pool` initializes a new `StakingPool` object, sharing it, and emits a `PoolCreated` event. The `fund_rewards` functions add `Coin` balances to the pool's respective reward balances, while `withdraw_rewards` functions allow the admin to remove rewards from the pool. `set_emissions` updates the daily reward emission rates for the pool, first updating the pool's rewards based on the current time, and `set_paused` allows the admin to pause or unpause the pool. Users can `stake` a `Position`
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": "0x746e748bd700e4ad7a32ea54f7e2a8cfd29be945bb6ab13ee6c4f34f96fb720c",
"n_tx": 2976,
"n_successful_tx": 2873,
"n_distinct_epochs": 57,
"n_distinct_sponsors": 0,
"first_seen_cp": 255796864,
"last_seen_cp": 283447295,
"first_seen_ts_ms": 1773871395274,
"last_seen_ts_ms": 1780666536806,
"total_gas_spent_mist": 16928065992,
"n_self_sponsored_tx": 2976,
"n_sponsored_tx": 0,
"gas_price_p50": 556,
"gas_price_p95": 557,
"active_hours_top24": [
21,
19,
6,
23,
17,
9,
16,
20,
22,
14,
11,
10,
15,
13,
12,
0,
7,
18,
1,
8,
5,
2,
3
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.
area + brightness = call volume; hover for detail