BITCOIN / ORDINALS / TIME # MACHINE
One block.
Every inscription.
Explore content written into Bitcoin. Read a block, look inside its inscriptions and keep a shared point of reference.
Ready. Choose a block or enter an inscription ID below.
Open an inscription or a series by ID
Paste a full ID (TXID + i + index), or up to 20 IDs, one per line. We read their creation blocks and verify the content.
Block results and a series are separate views. A series follows the supplied ID order.
Block verification & hashes
Header time is supplied by the miner; observation time comes from the device clock. Local times include their UTC offset, including during clock changes.
The list hash covers the block hash, parser version and ID order. Content hashes are separate. The complete Bitcoin chain is not verified locally.
Find a literal phrase in source text, JSON, HTML, JS, CSS, XML and SVG. Your phrase stays on this device. This is not a whole-chain search.
Read a block or an ID series, then enter a phrase.
Search covers the complete loaded text, independently of gallery filters. No OCR, decompression or fetching recursive dependencies. Skipped items are reported.
Compare observers
Transfer another observer's JSON report and paste it below. Matching data does not prove synchronized clocks.
Metadata & preview source
Inscription numbers and sats require an ord index. Fetch them using the button in the viewer. Images and text from a scanned block do not need this server.
CORS, CSP or server availability can limit access. The app does not silently switch sources. Numbers are displayed as claims from that index, without local confirmation.
Read a saved block
Use a .bin file, HEX or a JSON HEX string from /r/block. Choose fixed height and enter the height above first.
Tests & limits
We read newly revealed inscription envelopes, not transfers. The same parser can repeat the same error on two devices. Full parity with an independent ord index needs a separate comparison.
A phone may suspend the page in the background. On return, a surviving page can continue; after a reload, scan again. A closed page does not observe the network.
COMMON PHASE / SHARED MEMORY
The same point of reference.
Observers can share a block, content and a calculation rule. A common hash confirms those data. Clock calibration remains a separate measurement.
naka vintage · 🍌🦜
Author’s dedication: 3440413507773. Actual on-chain placement of this app is not yet verified. Select ★ on inscriptions to include them in the manifest.
Recursive reference after inscribing the manifest
Enter an inscribed manifest ID. We read its block and verify the JSON; the recursive loader pins the hash of that exact inscription. The gallery selection above does not replace it.
L0: clock uncalibrated. The manifest preserves the OBS-SYNC-1 vector but does not replace an L3 measurement. A hash is not a signature or an identity certificate.