btcintel
sign in

Luxor · block 975,493

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,493 to Luxor, by the payout address.

bitcoin-data mining pools · service data · 50 · in force since 11 Nov 2026

version
1 of 1
in force
in force since
11 Nov 2026
23:53 UTC
first read
11 Nov 2026
23:53 UTC
rests on
1
an output of the coinbase that pays a listed address
disputes
0
none open · none resolved

Attributions

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

what is said

pool
Luxor
how
by the payout address
source
bitcoin-data mining poolslicence: MIT
class
service data · 50from the service's own publication

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

what it rests on 1

payout address
32BfKjhByDSxx3BM5vUkQ3NQq9csZR6nt6output 1 of the coinbase pays it · the catalog lists it for this pool
matcher
v1
the source's file
sha256 ddc505c82dfa5868ce234be3ac0c05454bfbd6e1d34fd1e37f3004cde0a5ef0e

the days

the block was mined
11 Nov 2026 23:53 UTC
reported by the source
no report date: the record carries none
first read
11 Nov 2026 23:53 UTC
in force since
11 Nov 2026 23:53 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.

Everything said of block 975,493Dispute this claimnone open · none resolved

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:20869@v1 sha256:ab536a4ec3ee4cc5
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 11 Nov 2026 23:53 UTC by the pool matcher, v1in forcethis pagebtcintel:attributions:20869@v1 sha256:ab536a4ec3ee4cc5

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_20869?version=1" | grep -i etag# ETag: W/"ab536a4ec3ee4cc5f28f5656e6b572e883293f946c9f748cc1bf18dff3e9596d-gzip" curl -s "https://api.btcintel.io/v1/claims/att_20869?version=1" | jq -r .content_sha256# ab536a4ec3ee4cc5f28f5656e6b572e883293f946c9f748cc1bf18dff3e9596d# the first 16 hex are the citation's: btcintel:attributions:20869@v1 sha256:ab536a4ec3ee4cc5
it must give
ab536a4ec3ee4cc5f28f5656e6b572e883293f946c9f748cc1bf18dff3e9596d

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.