Luxor · block 975,629

block attributionin forceversion 1

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

mempool mining pools attributes block 975,629 to Luxor, by the payout address.

mempool mining pools · service data · 50 · in force since 13 Nov 2026

version: 1 of 1; in force
in force since: 13 Nov 2026; 04:10 UTC
first read: 13 Nov 2026; 04:10 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

subject: block 975,629 00000000000000000000b3221250ccdc2d666f73158549955d2833923d496821
pool: Luxor
how: by the payout address
source: mempool mining poolslicence: MIT
class: service data · 50from the service's own publication

Pool catalog: mempool/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 7ac47b0410134c2a023f09ae78aeb4161016f9528f748d987b6880b4cda19f9f

the days

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

Everything said of block 975,629 Dispute 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:21250@v1 sha256:9655a3ac4026e585
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

Version 1 · written 13 Nov 2026 04:10 UTC by the pool matcher, v1in forcethis pagebtcintel:attributions:21250@v1 sha256:9655a3ac4026e585

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_21250?version=1" | grep -i etag# ETag: W/"9655a3ac4026e585ddc32e52023578fc9099272fbb5315f6638e2f1f4a6d569d-gzip" curl -s "https://api.btcintel.io/v1/claims/att_21250?version=1" | jq -r .content_sha256# 9655a3ac4026e585ddc32e52023578fc9099272fbb5315f6638e2f1f4a6d569d# the first 16 hex are the citation's: btcintel:attributions:21250@v1 sha256:9655a3ac4026e585

it must give: 9655a3ac4026e585ddc32e52023578fc9099272fbb5315f6638e2f1f4a6d569d

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.