How to Read SupraScan for ElyxS

If ElyxS shows a transaction hash or SupraScan link, start there. Draw history, result verification, and profile history entries open the linked transaction.

For a prize claim or refund, after wallet confirmation you can also take the hash from wallet history.

If you already have a transaction hash, paste it into the SupraScan search field. If you are looking manually, use Blockchain -> Transactions, then open the relevant transaction.

Before checking fields, compare the SupraScan network with the network used by ElyxS and your wallet. On testnet, SupraScan shows a notice that the network keeps only recent data for a limited period. Save important transaction hashes as soon as you see them.

In Basic Information, start with quick checks:

• Status: a successful transaction is shown as Success.
• Sender: the wallet that signed the transaction.
• Recipient: the contract address or transaction recipient.
• Transaction Hash: the hash to compare with the ElyxS link or include in a support request.
• Function: the Move function called by the transaction, such as cancellation::cancel_draw, cancellation::claim_refund, or payout_processor::claim_payout.
• Time (Local): the local transaction time.

In Advanced Information, open the technical details:

• VM Status: for successful execution, it should show Executed successfully.
• Payload {...}: call data when SupraScan decodes it.
• Output {...}: the main block for event checks. Inside it, open Move -> events[].

Use the Events tab if SupraScan shows an event list for that transaction.

1. Open the transaction in SupraScan.
2. Go to Advanced Information.
3. Expand Output {...}.
4. Expand Move -> events[].
5. In each event, read the type line and the data object.
6. Use page search for the exact event name, such as WinnerRecordedEvent or RefundClaimPaidEvent.

type shows the event name. data contains the event fields: draw_id, winner, amount, request_id, reason_code, and other values to compare with ElyxS.

To connect the VRF request and result, compare request_id and draw_id in RandomnessRequestedEvent and RandomnessFulfilledEvent. They must refer to the same draw.

For draw cancellation, reason_code has two user-facing values:

• 1: insufficient participation by the sales deadline.
• 2: ticket cap reached without meeting the minimum participation requirement.

For payouts, PayoutStatusUpdatedEvent uses these statuses:

• 1: pending.
• 2: paid.
• 3: refunded.
• 4: expired.
• 5: non-monetary.
• 6: voided.

The amount, prize_amount, refund_amount, and ticket_price_amount fields are raw on-chain numbers. ElyxS shows users the formatted value.

For jackpot checks, ticket_index is a zero-based weighted ticket slot, not the participant's row number in the interface.

First check the network, transaction hash, and draw_id. Then confirm that you opened Output -> Move -> events[] or the Events tab.

If the event is still missing, do not replace it with another transaction that has a similar draw_id. Return to ElyxS and open the verification link again.

When contacting support, include your wallet address, draw ID, transaction hash, a SupraScan screenshot, and the field or event that does not match.

• Open Verify Draw Results if you want to start with the shorter user flow.
• Open Claim Prizes and Refunds if you are checking a payout or refund.
• Open Smart Contracts if you need contract and address context.
• Open Frequently Asked Questions if you want shorter answers about wallets, dVRF, and claims.