We use necessary cookies and optional analytics only with your consent.Cookie Policy

User GuidesUpdated: May 8, 2026

Verify Draw Results

How to open the verification path from ElyxS and compare the draw result with on-chain data in SupraScan.

Verification

How to confirm results and review the on-chain trail.

Start from the Hub

Open the relevant draw in Hub -> History and use the verification buttons in the draw entry. ElyxS will open the matching SupraScan record: this may be the request transaction, the result transaction, or, for a canceled draw, the cancellation transaction.

What to compare

When you review the result, compare:

  1. the draw you selected in ElyxS;
  2. the contract address shown for the platform;
  3. the SupraScan record opened by ElyxS;
  4. the final status and, when applicable, the payout shown after settlement.

Why this matters

The verification flow lets you confirm that the result was produced through the same on-chain process shown in the platform UI, instead of relying only on a front-end message.

You do not need to understand every technical detail to make a useful check. Matching the draw id, contract address, and the SupraScan record opened by ElyxS is already a strong transparency step.

If something looks inconsistent

  • Refresh ElyxS and reopen the draw from history.
  • Recheck that the explorer link matches the right draw.
  • Compare the contract address with the address shown in the ElyxS interface and opened by the explorer link.
  • If the discrepancy remains, contact support and include the draw id, transaction hash, and a screenshot.

Need help with this flow?

If the steps do not behave as expected, collect the basic context before you contact support.

  1. Confirm that the correct wallet and network are being used.
  2. Save the transaction hash, error code, or a screenshot of the failing step.
  3. If the flow is still blocked, send the key details to support.
Contact support

Helpful materials

FAQ, Glossary, and Error Reference are the fastest way to decode terms, errors, and adjacent product flows.

Open FAQ