Skip to main content
vet402
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 07:11 UTC · reused for up to 5 min
vet402Sellers · What to fix firstMethodology

x402.coinstats.app: x402 purchase results on Base, latest attempt 2026-09-27

15 Base listings. Latest result about the seller at each listing: 8 delivered · 0 failed on the seller's side · 0 with no such result among the attempts shown · 7 not tried yet. This counts, for each listing, the newest purchase that delivered or the newest failure on the seller's side. Attempts on vet402's side, not bought, not sorted, or awaiting on-chain verification are skipped.

By the latest attempt at each listing, whatever it was: 8 delivered · 0 failed on the seller's side · 0 on vet402's side · 7 not tried yet.

Latest attempt: 2026-09-27 12:02 UTC. This page read the ledger at 2026-09-29 07:11 UTC and reuses that read for up to 5 min.

1.Your listings

  1. x402.coinstats.app/insights/fear-and-greed/chartGET
    Latest attempt
    2026-09-27 12:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0xd396…6896 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: asking… · the full answerThe latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x7315aa41…8f40In export.csv?days=3: the row with attempted_at 2026-09-27T12:02:10Z and resource_key x402.coinstats.app/insights/fear-and-greed/chart.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-13 00:02 UTC · vet402's wallet was out of USDC · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))
      What vet402 recordedBetween 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).The 402 terms vet402 signed: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x84ef…f5a2 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
    2. 2026-09-03 07:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xeeb9063f…a1df
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x0750…162f. Input sent: body not recorded, query not recorded. The listing states no maxTimeoutSeconds vet402 could match; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x0750…162f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  2. x402.coinstats.app/portfolio/valueGET
    Latest attempt
    2026-09-27 00:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x5359…265b · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: asking… · the full answerThe latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xbb64ec5d…dc53In export.csv?days=4: the row with attempted_at 2026-09-27T00:02:21Z and resource_key x402.coinstats.app/portfolio/value.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-13 00:02 UTC · vet402's wallet was out of USDC · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))
      What vet402 recordedBetween 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).The 402 terms vet402 signed: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x2b62…e7f3 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
    2. 2026-09-04 01:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x1b41c2a6…df35
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x0750…162f. Input sent: body not recorded, query not recorded. The listing states no maxTimeoutSeconds vet402 could match; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x0750…162f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  3. x402.coinstats.app/wallet/blockchainsGET
    Latest attempt
    2026-09-23 12:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0xdd59…d561 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x89d07945…30b4In export.csv?days=7: the row with attempted_at 2026-09-23T12:02:19Z and resource_key x402.coinstats.app/wallet/blockchains.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-17 06:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x4fe0325a…5cba
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x6b29…9caf · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  4. x402.coinstats.app/tickers/marketsGET
    Latest attempt
    2026-09-23 00:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0xe7e3…18c8 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x34a94f79…4a52In export.csv?days=8: the row with attempted_at 2026-09-23T00:02:16Z and resource_key x402.coinstats.app/tickers/markets.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-13 00:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xa61ed47c…114b
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x5be2…5539 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  5. x402.coinstats.app/insights/fear-and-greedGET
    Latest attempt
    2026-09-23 00:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0xc0e8…5909 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerThe latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc34441ff…f60aIn export.csv?days=8: the row with attempted_at 2026-09-23T00:02:00Z and resource_key x402.coinstats.app/insights/fear-and-greed.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-16 18:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x3aee2023…7420
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0xe50a…9a68 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-10 01:01 UTC · Not bought: the 402 named another receiving address · not bought: vet402 did not paypayto_mismatch (the 402 named another receiving address, so nothing was paid) · HTTP — · no tx
      What vet402 recordedvet402 pays the receiving address the listing declares. The payTo in the 402 was a different address, so vet402 did not sign.The 402 vet402 saw: The 402 offered: exact · eip155:8453 · amount 1000 · asset 0x8335…2913 · payTo 0xa2AD…00c7 · maxTimeoutSeconds 300. At the time, the listing declared price 0.001 · payTo 0x0750…162f.
      Dispute this purchase
    3. 2026-09-02 19:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x9b39d6ab…3b3f
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x0750…162f. Input sent: body not recorded, query not recorded. The listing states no maxTimeoutSeconds vet402 could match; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x0750…162f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  6. x402.coinstats.app/fiatsGET
    Latest attempt
    2026-09-22 18:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x4082…2374 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x5c53f620…b422In export.csv?days=8: the row with attempted_at 2026-09-22T18:02:01Z and resource_key x402.coinstats.app/fiats.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-12 00:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf871f121…5917
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x596c…fd69 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  7. x402.coinstats.app/news/sourcesGET
    Latest attempt
    2026-09-22 12:10 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x12d3…6820 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x4b9a281e…d09fIn export.csv?days=8: the row with attempted_at 2026-09-22T12:10:00Z and resource_key x402.coinstats.app/news/sources.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-12 00:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xa60948e3…f970
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0xd713…f738 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-04 12:09 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x067bc83d…42e3
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x0750…162f. Input sent: body not recorded, query not recorded. The listing states no maxTimeoutSeconds vet402 could match; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x0750…162f · nonce 0x7a39…0307 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  8. x402.coinstats.app/marketsGET
    Latest attempt
    2026-09-18 18:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x35f3…ef70 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x9d6b5e4a…b292In export.csv?days=12: the row with attempted_at 2026-09-18T18:02:04Z and resource_key x402.coinstats.app/markets.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-11 18:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x9b263172…97c4
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xa2ad…00c7. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xa2ad…00c7 · nonce 0x0882…bad1 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-04 01:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc381e861…c3c2
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x0750…162f. Input sent: body not recorded, query not recorded. The listing states no maxTimeoutSeconds vet402 could match; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x0750…162f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  9. x402.coinstats.app/coinsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  10. x402.coinstats.app/coins/:coinIdGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  11. x402.coinstats.app/currenciesGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  12. x402.coinstats.app/exchange/supportGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  13. x402.coinstats.app/newsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  14. x402.coinstats.app/portfolio/coinsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  15. x402.coinstats.app/tickers/exchangesGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result (“Recorded (L1 paid purchase)”); a row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. The transaction link opens the settlement on Basescan. “Decision API now” is what the decision API (GET /api/v1/resources/{id}/decision?role=payer, no key) answers for the listing when you open this page; your browser asks it for the first 2 listings, and for the others when you ask. It is cautious for the payer: it leaves out the attempts that show vet402's fault, are held, or took no payment, and counts the rest, so it can say WARN or BLOCK for a listing whose failures this page leaves not sorted (API reference). Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.