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 defines a lottery system centered around a "LotteryState" object. Users can purchase lottery tickets using either SUI (seal_scroll) or JUI_ON_SUI tokens (burn_scroll, burn_scroll_v2, seal_and_burn). The system manages a prize pool and a house balance, both in SUI. Notable patterns include whale bonuses for larger JUI_ON_SUI purchases (check_whale_bonus, apply_whale_bonus), and the ability to add and spend "Faith Scrolls" which are a form of in-game currency. The package also includes administrative functions for managing the lottery, such as drawing winners, extending rounds, and adjusting parameters, often gated by "PilgrimageCap" or "TitheCap" objects.
This package defines a Blackjack game on Sui. The primary object types are `GameState` (stores global game parameters like prize pool, min bet, and pause status), `GameSession` (represents an active game for a player), and `PendingWithdrawal` (tracks initiated withdrawals). Public functions allow players to `place_bet` and `double_down` in a game session, depositing JUI_ON_SUI into the game's prize pool. An `AdminCap` holder can `settle` game sessions (distributing payouts based on game results), `set_paused` status, `set_min_bet`, and `initiate_emergency_withdraw` from the prize pool. Players can also `claim_timeout_refund` for inactive sessions after 24 hours. The game uses a vault/escrow pattern for the prize pool and an admin cap for privileged operations.
This Sui package, "tithe", manages two primary object types: TitheTracker and TitheAccount. The TitheTracker is a shared object that keeps a global count of total prepaid scrolls and total SUI received. TitheAccount objects are owned by individual users and track their remaining scrolls, total scrolls purchased, associated SUI paid, and a SUI balance. The public entry functions allow users to "prepay" for scrolls in two ways: `prepay` allows purchasing scrolls based on predefined tiers (1-5), while `prepay_custom` allows purchasing a custom amount of scrolls, with a minimum SUI payment. Both functions create a TitheAccount object for the payer, transfer the SUI into its internal balance, and update the global TitheTracker. The `allocate_scrolls` function allows a TitheAccount owner to allocate a specified number of their remaining scrolls to a Holy Lottery, depositing the corresponding SUI into the lottery's prize pool. This function requires a `TitheCap` (an admin capability from the holy_lot
This package implements a lottery system centered around a single shared object, LotteryState. Users can buy tickets using SUI or JUI_ON_SUI tokens, which are added to a prize pool (90% of SUI, 100% of JUI) and a house balance (10% of SUI). The admin can draw a winner, which transfers the entire prize pool to a randomly selected ticket holder, resets the tickets, and increments the round. Only the admin can draw a winner, transfer admin rights, or withdraw from the house balance. The contract also emits events for ticket purchases, JUI burns, winner draws, and round extensions.
This package defines a Blackjack game on Sui. The primary object types are `GameState`, which holds the game's overall state (prize pool, min bet, paused status, statistics), `GameSession`, representing an active game for a player, and `AdminCap`, granting administrative privileges. Public functions allow players to `place_bet` and `double_down` on a `GameSession`, contributing to the `prize_pool`. Admin functions (`set_paused`, `set_min_bet`, `initiate_emergency_withdraw`, `execute_emergency_withdraw`) manage game parameters and emergency withdrawals from the prize pool. The `settle` function, callable only by an admin, resolves a `GameSession`, distributing winnings from the `prize_pool` or triggering a jackpot. Notable patterns include an `AdminCap` for access control, a `prize_pool` acting as an escrow for bets and winnings, and time-gating for `claim_timeout_refund` and `execute_emergency_withdraw` functions.
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.
Tinted amber on the bubble map when they appear in the expanded graph.
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": "0x3a3f29ca5e2a3e1dc65ba00a41481da21bddf63f85b9db89bca86d000ac92e32",
"n_tx": 5098,
"n_successful_tx": 5062,
"n_distinct_epochs": 76,
"n_distinct_sponsors": 0,
"first_seen_cp": 256978855,
"last_seen_cp": 283581458,
"first_seen_ts_ms": 1774171007112,
"last_seen_ts_ms": 1780696706932,
"total_gas_spent_mist": 6263836708,
"n_self_sponsored_tx": 5098,
"n_sponsored_tx": 0,
"gas_price_p50": 557,
"gas_price_p95": 557,
"active_hours_top24": [
21,
14,
20,
19,
13,
22,
15,
5,
23,
12,
18,
17,
16,
9,
8,
2,
10,
6,
1,
0,
3,
4,
7,
11
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0.4,
"bot_signals": [
"timing_automation"
],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.
area + brightness = call volume; hover for detail