blockrun.ai/api/v1/pm/polymarket/markets/27146956652877944551877724690365745048289675287536243265951843487691050802191/volume
1.Catalog declaration
| Resource URL | https://blockrun.ai/api/v1/pm/polymarket/markets/27146956652877944551877724690365745048289675287536243265951843487691050802191/volume |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6e007731870ede419cfb31889cd5c4493cecb04c |
| Declared price (base units) | 8500 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-14 21:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 191 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 2191 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 208 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 1147 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 500 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 866 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 578 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 162 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 155 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 212 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 56 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 300 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 of those also returned a 2xx response (delivered). 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 also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 match- the response had the fields the listing's output schema declares.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-16 12:082026-09-16 12:08 UTC | settled (nonce-bound) | 200 | 0x8b01b56f…1775 | 2602 ms |
| 8500 units (≈ $0.0085 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/da9aaf5e-e3a2-4f41-a29e-9463fa5dc227)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-07 | delisted | {"status":"active"} | {"status":"delisted"} |
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.