x402.pulsescanner.io/v2/validators/slashed
1.Catalog declaration
| Resource URL | https://x402.pulsescanner.io/v2/validators/slashed |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x4842a7d5b2553f4385d5e8d0cf1b94a10b99dba7 |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-10-21 01:01 UTC / 2026-11-12 16:05 UTC |
| Catalog-reported calls / payers (30d) | 12 / 8 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-12 16:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-11-10 16:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-11-08 13:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-11-06 04:40 UTC | GET | pass | 402 | 208 ms | — |
| 2026-11-03 21:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-11-01 04:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-10-30 04:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-10-28 04:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-10-26 15:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-10-24 16:47 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-22 16:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-10-21 10:30 UTC | GET | pass | 402 | 29 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 11-03 17:022026-11-03 17:02 UTC | settle_failed | 503 | — | Base | 1707 ms |
| 3000 units (≈ $0.003 USDC) · L2 not_checkedWhose side: not sorted: one failure so far | |||||
4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight. If it was right, it stands. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.
About the purchase at 2026-11-03T17:02:06Z (UTC). The form starts with that time; add what you saw instead.