Network activity log
Every line here is a transaction that confirmed. Nothing is simulated, sampled or reconstructed — when the chain is quiet the log is short, and it stays short.
The log
Loading…
Reward epochs
A reward epoch is one full cycle: fee revenue arrives, an allocation is made, the reward asset is bought, holder balances are snapshotted at a block, and the epoch is published with a Merkle root that wallets claim against. These are the same records as the log above, grouped so the sequence reads in order.
Loading…
What gets logged
| Event | What it records |
|---|---|
| fee_received | Project fee revenue arriving at the fee vault. |
| fee_allocated | That revenue being split to its destinations on-chain. |
| reward_swap | Fee revenue buying the reward asset for a holder epoch. |
| reward_snapshot | The block at which holder balances were read for an epoch. |
| reward_epoch_published | An epoch’s Merkle root published, which is what makes claiming possible. |
| reward_claimed | A holder claiming their share of a published epoch. |
| leaderboard_finalized | A day’s high score board closing and being locked. |
| leaderboard_payout | The daily top 10 being paid on-chain. |
| asset_verification | A check of the reward asset against Robinhood’s own registry. |
A transaction that is still pending, or that reverted, is never shown here as confirmed. An entry is written only after its record confirms on-chain, which is why this log can lag a wallet by a block or two and why it never runs ahead of one. If an event kind above is missing from the log, it has not happened yet.
Reward epochs are summarised on the rewards page, and daily payouts are linked from the high score board.