L'API de l'explorateur

Params

none

Retour

a flat object of counters

Chain-wide counters: block and transaction totals, wallets, gas used, the cadence figures the node reports, the mini-block head, index lag and the spool's own health.

Aussi à. GET /

Bon à savoir. Recomputed once a second by a background thread and served from a cache for six tenths of a second, so two calls in the same instant give the same answer. It also carries a rate counter this reference does not quote: the site publishes no throughput figure, and the number is local anyway.

Params

none

Retour

{stats, charts, blocks, txs, topAccounts}

The explorer's front page in one call: the cached stats, 48 chart points, the 8 most recent blocks that carried transactions, 12 transactions and the 8 busiest accounts.

Bon à savoir. Use this instead of five calls. Its parts are the other routes' defaults and nothing about it is configurable.

Params

limit (default 48, clamped to 200)

Retour

[{number, timestamp, txCount, gasUsed}]

A bare array, oldest first.

Bon à savoir. It prefers blocks that carried transactions and falls back to all blocks only when fewer than four match, so the series is not evenly spaced in time and must not be read as one.

Params

limit, offset, active=1

Retour

[{number, hash, timestamp, gasUsed, txCount, miniCount}]

A bare array, newest first. `active=1` returns only blocks that carried transactions.

Bon à savoir. No total is returned, so there is nothing to page against except asking until you get a short answer.

Params

limit, offset over the block's transactions

Retour

one block with its transactions and mini-blocks

The number is parsed permissively: decimal and 0x both work.

Bon à savoir. `limit` defaults to 50 here rather than 25, and the mini-blocks fall back to a live read against the node when the index has none for the block. 404 when unknown.

Params

limit, offset

Retour

{total, minis: [...]}

Mini-blocks, newest first. One of the few routes that does return a total.

Bon à savoir. Timestamps are `timestamp_us`: MICROSECONDS, not seconds, and a decimal number rather than a hex quantity.

Params

limit, offset over the transactions

Retour

one mini-block

By decimal number or by hash.

Bon à savoir. When the index does not have it, the service asks the node - and the answer then ALSO carries `stateDiffHash`, `sequencerSig` and `receipts`, which the indexed answer does not. The shape depends on where it was found.

Params

limit, offset

Retour

a bare array, newest first

Transaction summaries.

Bon à savoir. No total.

Params

none

Retour

the full transaction

The richest object in the API: input data, the decoded method for known selectors, logs with labelled addresses, CALL TRACES, token transfers and NFT transfers.

Bon à savoir. The traces are the reason this route exists. The node exposes no debug namespace at all, so there is nowhere else on this chain to get them. 404 when unknown.

Params

none

Retour

{deployed, router, split, burn, launches, arcadeSkims, deferred, claimed, pendingEthWei, ...}

Everything the fee split has done and everything still waiting, read from the log spool rather than over RPC.

Bon à savoir. `{"deployed": false}` and NOTHING ELSE when the fee layer is not in the manifest - that is an ordinary state, not an error, because that layer is deployed by hand. The ether side and the token side are kept as separate figures and never summed.

Params

limit, offset

Retour

{total, accounts: [...]}

Accounts ordered by how much they have transacted.

Bon à savoir. The ordering is by transaction count, not by balance.

Params

limit, offset over the transaction lists

Retour

the largest payload in the service

Balance, nonce, counts, whether it is a contract, its creator and what it created, token and NFT holdings with metadata, the name-service record, and recent transactions and transfers.

Bon à savoir. `bytecode` is TRUNCATED to 400 hex characters with an ellipsis appended; `bytecodeSize` is the real length. The whole answer is cached for a few seconds under a key that includes the paging, so two different pages are two different cache entries.

Params

none

Retour

a list of at most 40 tokens

PKL pinned first, then by transfer count. Each entry merges a live probe of the contract with the operator's registry entry.

Bon à savoir. Forty is a hard cap and there is no paging past it. An address that probes as an NFT is skipped even if the registry calls it a token.

Params

none

Retour

{nfts: [...]}

At most 40 collections, verified ones first, then by how many have been minted.

Bon à savoir. The collection list is DISCOVERED from transfer logs rather than registered, so a collection nobody has traded is absent.

Params

limit, clamped to 48

Retour

the collection, its items and its 30 most recent transfers

Collection metadata merged from the chain and the registry.

Bon à savoir. Items are fetched one at a time up to the clamp, and off-chain metadata is resolved by a BACKGROUND thread - so the first request for a cold collection returns items whose metadata is still missing, and a second request a moment later returns more. Held for fifteen seconds in a cache of its own.

Params

none

Retour

one item plus `collectionMeta`

One token of a collection.

Bon à savoir. The token id must be all digits, or the path does not match this route at all and you get the 404 for an unknown route.

Params

none

Retour

{name, label, available, reserved, owner, resolved, expires, price, twitter, website, description}

A name-service lookup, read live from the registry contract.

Bon à savoir. A trailing suffix is stripped, and the label must be 3 to 32 characters. A name outside that range, and any lookup at all when the name service is not configured, is a 404 - which is indistinguishable from a name that does not exist.

Params

none

Retour

raw image bytes

The only non-JSON, non-stream route. The content type is inferred from the stored file's extension.

Bon à savoir. 404 as JSON when there is no logo, so a client must check the status before treating the body as an image.

Params

none

Retour

text/event-stream, one stats frame per update

Server-sent events carrying the same object /stats returns, pushed when it changes.

Bon à savoir. Bounded to 32 concurrent streams - the 33rd gets 503 - and the server CLOSES every stream after five minutes. A client that does not reconnect simply stops receiving, with no error.

Params

none

Retour

204

The preflight. Allowed methods are GET and OPTIONS, allowed header is Content-Type.

Bon à savoir. 403 when an Origin is present and not on the allowlist, rather than a 204 without the allow header.

Params

none

Retour

405

This API is read-only and answers 405 to every POST, in JSON and with the CORS headers.

Bon à savoir. It had one write route: a token-metadata edit signed by the contract's owner. It is gone, along with the form that called it, because an explorer that takes visitor-supplied identity for an asset is an impersonation surface.