Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago
intel.chainquery.com/v1/coin-velocity
1.Catalog declaration
| Resource URL | https://intel.chainquery.com/v1/coin-velocity |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x7cf45cd775bdf31a5a96fa0a5805df0b610d87ff |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
2026-08-142026-10-19
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 325 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 452 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 508 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 89 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 334 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 624 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 363 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-25 10:31 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 38 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 43 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 81 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
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
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. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.