RPC activity

A public view of the apps building on Nano.

Add your app

Total requests

—Loading activity…

Attributed requests

—

Active apps

—With attributed requests

Request volume

Totals and app rankings include all actions.

AttributedUnattributedTotal

Aggregate requests · UTCLoading…

RPC actions

By volume

Select an action to filter statistics

Applications

Share of requests

Select an app to explore its activity.

#	Application	Requests	Share

Optional app attribution

Put your app on the map.

Include these two headers to show your app in the statistics. Keys linked to an app are attributed automatically.

HTTP request headers

HTTP-Referer: https://subnano.me
X-Title: Subnano

Optional and self-reported. No valid headers? Requests still work and count as Unattributed.

How the data works

Daily aggregate counts. All dates in UTC.

Privacy by design

App activity, without user data.

The attribution database stores daily counters by app and RPC action, app names and sanitized public app URLs. It stores no IP addresses, wallet addresses, RPC payloads, API keys or individual request records. No cookies or third-party analytics.

What is counted, and how attribution works

Counts include valid HTTP RPC requests accepted after authentication, rate limiting and validation, including cached responses and proof of work. Early rejections, preflights, page views and WebSocket messages are excluded.

A saved app association on a valid API key takes priority over headers. Otherwise, HTTP-Referer identifies a public website or GitHub repository and X-Title supplies an app name, up to 80 characters. Invalid or missing headers count as Unattributed.

Website paths, queries and fragments are discarded. GitHub URLs retain only the repository path. App labels provided by headers are self-reported. Attribution does not change RPC permissions or limits.