tenjin.blog
https://tenjin.blog/api/read/0x8819c74dc18fc05d8c4d761e5a1ced6bada86836/why-x402scan-shows-zero-transactions-on-a-server-that-is-paid-correctlyShares a payout wallet with 2 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Why x402scan shows zero transactions on a server that is paid correctly. If you run an x402 resource server, settle payments correctly, and still see a flat zero on your x402scan dashboard, the explanation is almost always attribution, not a lost payment. I hit this on a production x402 resource server where money was arriving on-chain exactly as designed and the explorer still credited us with nothing. Here is what is actually happening, verified as of July 2026 against the Merit-Systems/x402scan indexer behavior. x402scan builds its picture of a server from two thi. One payment returns the full text, and the creator is paid as it is used.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 121ms · p95 259msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/7/2026, 12:00:00 AM | 100% | 15 | 124ms |
| 9/8/2026, 12:00:00 AM | 100% | 21 | 118ms |
| 9/9/2026, 12:00:00 AM | 100% | 20 | 124ms |
| 9/10/2026, 12:00:00 AM | 100% | 14 | 112ms |
| 9/11/2026, 12:00:00 AM | 100% | 10 | 114ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 177ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 112ms |
| 9/14/2026, 12:00:00 AM | 100% | 15 | 119ms |
| 9/15/2026, 12:00:00 AM | 100% | 16 | 118ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 128ms |
| 9/17/2026, 12:00:00 AM | 100% | 15 | 125ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 121ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 113ms |
| 9/20/2026, 12:00:00 AM | 100% | 12 | 114ms |
| 9/21/2026, 12:00:00 AM | 100% | 12 | 126ms |
| 9/22/2026, 12:00:00 AM | 100% | 12 | 118ms |
| 9/23/2026, 12:00:00 AM | 100% | 13 | 119ms |
| 9/24/2026, 12:00:00 AM | 100% | 13 | 118ms |
| 9/25/2026, 12:00:00 AM | 100% | 13 | 130ms |
| 9/26/2026, 12:00:00 AM | 100% | 13 | 117ms |
| 9/27/2026, 12:00:00 AM | 100% | 13 | 120ms |
| 9/28/2026, 12:00:00 AM | 100% | 12 | 122ms |
| 9/29/2026, 12:00:00 AM | 100% | 12 | 118ms |
| 9/30/2026, 12:00:00 AM | 100% | 12 | 126ms |
| 10/1/2026, 12:00:00 AM | 100% | 13 | 124ms |
| 10/2/2026, 12:00:00 AM | 100% | 12 | 120ms |
| 10/3/2026, 12:00:00 AM | 100% | 12 | 116ms |
| 10/4/2026, 12:00:00 AM | 100% | 10 | 122ms |
| 10/5/2026, 12:00:00 AM | 100% | 10 | 136ms |
| 10/6/2026, 12:00:00 AM | 100% | 9 | 116ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- 0
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- self-hosted
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Namecheap
- Domain registered
- 2026-04-21
- Hosting network
- VERCEL-01
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Settlement totals · last payment 7/24/2026