Using the explorer

The Somnia Explorer shows Somnia Oracle activity at somnia-platform-explorer.vercel.app/oracle. Use its chain selector to switch between Global (mainnet) and Global testnet. Every page shows data for the selected network. To submit a question, connect a browser wallet with the button in the top bar.

Page	Path	What it shows
Questions	/oracle	Upcoming and past questions, with search and filters
Question	/oracle/questions/<id>	One question's definition, timeline, per-source results, agent receipts and answer
Templates	/oracle/templates	Ready-made questions to configure and schedule
Schedule	/oracle/schedule	A form to build and submit any question from your wallet
Sources	/oracle/sources	Every source, its usage and success rate, grouped by who serves it
Source	/oracle/sources/<id>	One source's decoded params, recent reads and the questions using it
Status	/oracle/status	Protocol throughput, stuck questions, indexer sync and contract balances

Questions

/oracle opens with network-wide counts: questions, upcoming, resolved, voided and distinct sources. Below them:

• Upcoming lists open questions by resolution time, soonest first. Past lists resolved and voided questions, most recent first.
• Asked by me shows only the connected wallet's questions.
• Search matches display names and question text. You can also filter to Numeric or Discrete questions.

Each card shows the question's status, answer type and Caliber rating, when it resolves or resolved, its outcomes with the winner highlighted, its creator and how many sources it reads. A Stuck badge means its resolution trigger failed; see Status. Select a card to open the question.

Question detail

/oracle/questions/<id> shows everything about one question:

• The question: its display name, full text, creator, answer type and Caliber rating, plus the advisory moderation verdict.
• Valid answers: the discrete labels, or the numeric intervals drawn on a scale, with the winning outcome marked.
• Timeline: submitted, scheduled, dispatched and resolved, with the transaction for each step.
• Configuration: minAgreement, subcommittee size and threshold, and the fee paid.
• Sources: each source's decoded params and what it returned for this question: the value or label, or why it failed. Sources that contributed to the answer are marked.
• Agents: every agent request the question made. Each links to the request's page in the Somnia Agents section and to every validator's receipt, the step-by-step log of what each agent fetched and returned. This is where to look when a question voids.
• Answer: the outcome and value, or the void reason.

From a question you can copy it into the Schedule form as a new question, to ask the same thing at another time.

Templates

/oracle/templates offers ready-made questions in categories such as crypto, FX, stocks, social, sport, macro, markets, weather and energy. Pick one, fill in its few inputs (a token and a time, a team and a date), and preview the exact question it will schedule, sources and all. Continue to open the Schedule form with everything filled in.

Templates use sources known to resolve well, with timestamps baked into the URLs where the source allows, so they tend to rate highly.

Schedule

/oracle/schedule builds any question by hand: the question text, the answer type with its labels or intervals, up to 20 Website, JSON or Contract sources, the resolution time and the agreement rules. Guided JSON sources cover common APIs, so you don't have to write URLs and paths yourself.

The form previews what each source returns now, checks the definition against the protocol's rules, and shows the live fee from getSubmissionCost. Submitting sends submitQuestion from your wallet with that fee. See Asking questions for how to fill each field in.

Sources

/oracle/sources lists every source the oracle has seen. Sources are content-addressed, so the same URL, path or contract call across many questions is one row, with its usage count and success rate. You can filter by type and search, or browse by authority: the site, API or contract that serves the data.

/oracle/sources/<id> shows one source's decoded params, what it fetches, its recent agent requests, contract reads and per-question answers, and every question that uses it. Use it to check a source's track record before relying on it. See Sources for the encodings.

Status

/oracle/status shows the oracle's health, refreshed every 10 seconds:

• Protocol: total, in-flight, resolved and voided questions, the resolution rate (resolved out of resolved plus voided) and the median time from a question falling due to its answer landing.
• In-flight pipeline: how many questions are submitted, scheduled and awaiting answers.
• Stuck questions: open questions whose Reactivity trigger failed. Anyone can call triggerMissedSchedule on OracleCore to dispatch them, or voidExpired an hour after their resolution time. See Timing and stuck questions.
• Indexer: the last block the oracle indexer has processed against the chain head, the lag in blocks and the events processed. Every other page reads from this indexer, so a large lag means they are behind the chain.
• Contracts: the native-token balance of OracleCore, OracleEntryPoint and the two registries, each linked to the explorer. OracleCore pays for Reactivity callbacks and must stay above its reactivity floor (32 SOMI on mainnet, 32 STT on testnet); below it, scheduled questions can fail to dispatch. The page warns when it is within 10% of the floor and flags it below.