btcintel

Ocean.xyz · block 975,683

block attributionin forceversion 1

The attribution of one block to a pool by one source, bitcoin-data mining pools. The block's page lists every source's attribution, side by side.

bitcoin-data mining pools attributes block 975,683 to Ocean.xyz, by the tag in its coinbase.

bitcoin-data mining pools · web crawl · 20 · in force since 13 Nov 2026

version
1 of 1
in force
in force since
13 Nov 2026
14:10 UTC
first read
13 Nov 2026
14:10 UTC
rests on
1
a match of the catalog's pattern in the coinbase's text
disputes
0
none open · none resolved

Attributions

the claim · what it says, what it rests on, since when

what is said

how
by the tag in its coinbase
source
bitcoin-data mining poolslicence: MIT
class
web crawl · 20read on a public web page

Pool catalog: bitcoin-data/mining-pools (MIT)

what it rests on 1

text found in the coinbase
< OCEAN.XYZ >
the catalog's pattern
OCEAN.XYZ
how it matched
the text contains the pattern
matcher
v1
the source's file
sha256 ddc505c82dfa5868ce234be3ac0c05454bfbd6e1d34fd1e37f3004cde0a5ef0e

the days

the block was mined
13 Nov 2026 14:11 UTC
reported by the source
no report date: the record carries none
first read
13 Nov 2026 14:10 UTC
in force since
13 Nov 2026 14:10 UTC
file read
not served: the record carries the file's hash and no time

An attribution is one source's reading of one block by one method. The block's page lists every source's, in one fixed order and with no winner.

The record

cite it · its versions · check that what you quote is what is served

Citea citation names one claim at one version

citation
btcintel:attributions:21401@v1 sha256:404e87db418e75ae
this version
the link that pins version 1it keeps showing version 1 when a later one is written
as a file
a block attribution is not exported as STIX: the API serves no file for it

Versions1 version

  1. Version 1 · written 13 Nov 2026 14:10 UTC by the pool matcher, v1in forcethis pagebtcintel:attributions:21401@v1 sha256:404e87db418e75ae

Verifythe hash of what is served must begin with the citation's 16 hex

A citation names a claim, a version and the first 16 hex of that version's content hash. Fetch the version and compare: the hash must begin with the citation's 16 hex. The ETag of the answer carries the same hash: production answers it weak (W/) and with its encoding's suffix (-gzip), or bare.

curl -sI "https://api.btcintel.io/v1/claims/att_21401?version=1" | grep -i etag# ETag: W/"404e87db418e75ae672623a5022f49ab56d0a7a080234e73d9442f6f903e4bd0-gzip" curl -s "https://api.btcintel.io/v1/claims/att_21401?version=1" | jq -r .content_sha256# 404e87db418e75ae672623a5022f49ab56d0a7a080234e73d9442f6f903e4bd0# the first 16 hex are the citation's: btcintel:attributions:21401@v1 sha256:404e87db418e75ae
it must give
404e87db418e75ae672623a5022f49ab56d0a7a080234e73d9442f6f903e4bd0

Every change to the content writes a new version with its own hash; the previous version keeps its hash and its citation, so a quote never changes under the reader.