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
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
55.8% avgResponse time
p50 118ms · p95 222msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/15/2026, 9:00:00 AM | 100% | 2 | 132ms |
| 8/15/2026, 11:00:00 AM | 100% | 1 | 122ms |
| 8/15/2026, 12:00:00 PM | 100% | 1 | 112ms |
| 8/15/2026, 1:00:00 PM | 100% | 1 | 106ms |
| 8/15/2026, 2:00:00 PM | 100% | 1 | 109ms |
| 8/15/2026, 3:00:00 PM | 100% | 1 | 140ms |
| 8/15/2026, 4:00:00 PM | 100% | 1 | 186ms |
| 8/15/2026, 6:00:00 PM | 100% | 1 | 122ms |
| 8/15/2026, 7:00:00 PM | 100% | 1 | 231ms |
| 8/15/2026, 8:00:00 PM | 100% | 1 | 115ms |
| 8/15/2026, 9:00:00 PM | 100% | 1 | 126ms |
| 8/15/2026, 10:00:00 PM | 100% | 1 | 212ms |
| 8/15/2026, 11:00:00 PM | 100% | 1 | 108ms |
| 8/16/2026, 1:00:00 AM | 100% | 1 | 118ms |
| 8/16/2026, 2:00:00 AM | 100% | 1 | 111ms |
| 8/16/2026, 3:00:00 AM | 100% | 1 | 123ms |
| 8/16/2026, 4:00:00 AM | 100% | 1 | 105ms |
| 8/16/2026, 5:00:00 AM | 100% | 1 | 104ms |
| 8/16/2026, 6:00:00 AM | 100% | 1 | 102ms |
| 8/16/2026, 8:00:00 AM | 100% | 1 | 156ms |
| 8/16/2026, 9:00:00 AM | 100% | 1 | 266ms |
| 8/16/2026, 10:00:00 AM | 100% | 1 | 111ms |
| 8/16/2026, 11:00:00 AM | 100% | 1 | 103ms |
| 8/16/2026, 12:00:00 PM | 100% | 1 | 127ms |
| 8/16/2026, 1:00:00 PM | 100% | 1 | 104ms |
| 8/16/2026, 3:00:00 PM | 100% | 1 | 116ms |
| 8/16/2026, 4:00:00 PM | 100% | 1 | 117ms |
| 8/16/2026, 5:00:00 PM | 100% | 1 | 125ms |
| 8/16/2026, 6:00:00 PM | 100% | 1 | 114ms |
| 8/16/2026, 7:00:00 PM | 0% | 1 | — |
| 8/16/2026, 8:00:00 PM | 0% | 1 | — |
| 8/16/2026, 10:00:00 PM | 0% | 1 | — |
| 8/16/2026, 11:00:00 PM | 0% | 1 | — |
| 8/17/2026, 12:00:00 AM | 0% | 1 | — |
| 8/17/2026, 1:00:00 AM | 0% | 1 | — |
| 8/17/2026, 2:00:00 AM | 0% | 1 | — |
| 8/17/2026, 3:00:00 AM | 0% | 1 | — |
| 8/17/2026, 5:00:00 AM | 0% | 1 | — |
| 8/17/2026, 6:00:00 AM | 0% | 1 | — |
| 8/17/2026, 7:00:00 AM | 0% | 1 | — |
| 8/17/2026, 8:00:00 AM | 0% | 1 | — |
| 8/17/2026, 9:00:00 AM | 0% | 1 | — |
| 8/17/2026, 10:00:00 AM | 0% | 1 | — |
| 8/17/2026, 12:00:00 PM | 0% | 1 | — |
| 8/17/2026, 1:00:00 PM | 0% | 1 | — |
| 8/17/2026, 2:00:00 PM | 0% | 1 | — |
| 8/17/2026, 3:00:00 PM | 0% | 1 | — |
| 8/17/2026, 4:00:00 PM | 0% | 1 | — |
| 8/17/2026, 5:00:00 PM | 0% | 1 | — |
| 8/18/2026, 6:00:00 PM | 0% | 1 | — |
| 8/19/2026, 6:00:00 PM | 0% | 1 | — |
| 8/20/2026, 6:00:00 PM | 0% | 1 | — |
- Availability
- 17
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- 1
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 12% — 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)
Payments per day
last payment 7/24/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 7/24/2026 | 2 | 0.1 | 2 |
This payout wallet is shared: figures cover all 4 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.