XPlorer following the chain as its own read-only node

height 23746 of 23746 on the network. 9 peer(s) connected, 77 in its peer directory; 1042 block(s) followed and 866 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.

What this follower is, locally

Following 7 seed(s) — their addresses are not published here, for the reason the peer table gives. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.

M 5.2 · 97 km ESE of Kyzyl-Eshme, Kyrgyzstan

39.3319° N73.3673° E2026-11-03 21:34:08.563 UTCM 5.2

A GodCypher timestamp: this earthquake as the observatories below reported it, timed against the national time labs, digested, sealed and counter-validated by GodCypher. Its anchor on the chain is pending.

Depth: 10.0 km
Place: 97 km ESE of Kyzyl-Eshme, Kyrgyzstan
Observatories agreeing: 2 of 5: USGS, GFZ
Independent solutions: gfz, usgs
Signed time: 3 of 3 Roughtime servers asked signed the digest, verified against the pinned server keys
Record made: 2026-11-03 21:53:36.324 UTC
Timestamp id: 5359d27b6be4b0a2c2c36d2e766112fc7ed4b9eea615b8da21f2716bcd6b5c65 · version jord-v2
GodCypher: CountersignedNot sealed
Anchor: Pending

What each observatory reported

Each observatory’s own values and event id. The distance and the seconds are from the timestamp’s own epicentre and origin time.

Observatory	Event id	Origin time (UTC)	Epicentre	From the print	Depth	Magnitude	Source, as text
USGSUnited Statesagrees	`us7000tvtj`	2026-11-03 21:34:08.563 UTC±0.00 s from the timestamp	39.3319° N, 73.3673° E97 km ESE of Kyzyl-Eshme, Kyrgyzstan	0.0 km	10.0 km	5.2 mww	`https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson&eventid=us7000tvtj`
EMSCFrancerelays usgs	`20261103_0000294`	2026-11-03 21:34:08.563 UTC±0.00 s from the timestamp	39.3319° N, 73.3673° ETAJIKISTAN	0.0 km	10.0 km	5.2 mw	`https://www.seismicportal.eu/fdsnws/event/1/query?format=text&eventid=20261103_0000294`
GFZGermanyagrees	`gfz2026vosq`	2026-11-03 21:34:11.040 UTC+2.48 s from the timestamp	39.4230° N, 73.2950° ETajikistan-Xinjiang Border Region	11.9 km	10.0 km	5.0 M	`https://geofon.gfz.de/fdsnws/event/1/query?format=text&eventid=gfz2026vosq`

The atomic watch when the record was made

2026-11-03 21:53:34.186 UTC: this host's clock is 2.781 ms behind the national time laboratories (median of 9 of 9, good to about ±10.373 ms), inside the 250 ms tolerance.

Median offset +2.78 ms, verdict in step.

Each tick is one lab. Zero is this explorer’s own clock; the tall mark is the median.

Time lab	Host	Offset	Round trip	Stratum	Used
NIST	`time.nist.gov`	+5.01 ms	124.3 ms	1	yes
PTB	`ptbtime1.ptb.de`	+2.98 ms	15.7 ms	1	yes
NPL	`ntp1.npl.co.uk`	+2.78 ms	14.4 ms	1	yes
METAS	`ntp.metas.ch`	+3.13 ms	10.1 ms	1	yes
INRIM	`ntp1.inrim.it`	−0.66 ms	28.6 ms	1	yes
NICT	`ntp.nict.jp`	+1.91 ms	216.9 ms	1	yes
SYRTE	`ntp-p1.obspm.fr`	+2.23 ms	20.7 ms	1	yes
VSL	`ntp.vsl.nl`	+0.19 ms	16.3 ms	1	yes
RISE	`ntp1.sp.se`	+3.16 ms	21.9 ms	1	yes

Digest and seal

The digest covers the timestamp’s values; the seal is SourceLess’s signature over the digest.

Digest: 5359d27b…cd6b5c65
Seal scheme: aegis-gemini
Signer: zk13str_b4c421607b749197aff78f3edb58ce087a7a16b6_16a1
Signature: 1f7a00c3e7e8c31c7af40997b63f88853a901b39ea49e49596767bb72e8038e16801505c7145053ca4551ec40c231ec423c833d11a500ef5c83315035fdea507
Post-quantum signature: 21718711…0d12191d
The whole signature, 3,309 bytes
2171871123b9d1f993ab49bc7d2dcf0afdb3c1aa44fd52c94566e47179ba6f81eeacf359bc5788c813b7b63f777e91e5d5b0a6f5cd64e499df478ce42d66aad12b4a0cbd0f90959242d1f65505029d6ffb53f2e1b444de54466b47acb39d84dfe044fe2b1d9b55521faafad82dcf4368f1cf04b183023b4bfbae7190d651ceaa55b5978c3888fd66cef997b00c53cf544f81180c523e4ca43bcd05000823f7cf145dbf90818bc89159319c092acb0188dbb657d4fc8f3f81dbbb7ff5cd6adb136ec0504aa03a95b7e5a4fd934e79d9f44fef1eccc0b457c71aa4aa26c3281e3e9aba650001b3f8525d97934dcd5b4d53072fdc1672123f502d151a0469f8c23fe961fdde0d0b8970f8117d80738ca19fac697c6c06d1f370d8ca08cc99b67693c80911ad70b561ca420d79a951ee95550cf7b326e7422899664dbc4043185f06bc69214dae9e3902a006d7dcb2e09ff7dec1b10a3361433c9baf1a1e164c97a18f4006842fdd77e0451d885d3496da2d363450d094d78732c72968b025c49688a66f1750b96ecd86279833334c23151ad6159e33b9781400071a6727b279bef595d4d4e99fa99894c3a40462cabd4c8b640cd58cd78cedf8b99815891a3e8cb4e162e662fc799c3d83c7c9ebb3d036601f686c763e24293057ff2075e0c25a15b889ac4354083308aadd3a0e45df1b5c9790fadd9277f2c338de8059176a57d2c9888d8c64fd8360f1531a41241b08661898575ef8dfc641002a36028298410502593dcc11407743f29b1c01999c6777f9d344faeea014bcd8f01121f0a665766bd109b794f0fb071804a7159500239f1b2024b1e6092c71fc8ee0b532fda51c6421762c0747768f9ec90343c424a501f7b96b24cc536a71a08501566d6d59bce9f702d9000d106a607c420fca09320423d3409d621ebdd692caedd6bb9c0278d378b84d6dc178ff2110b522c126856e2574f12e57ad95642e001bc13574a4b6615e1a19d79ff9e959c2f896cb99e5a4417656b2db35c885e8abee2c00f5e3e87fda855056e0cddc671cdb73a47e44c330a07efd5018fd4f7cd4ce5ec0c2d46707943731f2703152080bd1931b7e4aba25ecc956454dc68d3f64d5a54f780d58d68cc2bbb0bdae7279c59ffd039102097ea557e1c17e852c9ba591f508ffb0787e32c70c19a95368f0ec1b73a1f412411a683fe27621973e2ed4df69bdeff1f0bc69513f82f9cba9dc2d6384197ba1e23e5a60cb743ed4f92a6f48cd35cd1f612d011a820785b7ff2149587de0ed98a7ee01327d78213d161f893af0fa7c665b2939996ee0cb2cac73dfb5f04bf00ab9d16c4cfa2e9f092a2306c21c6433ffc0035d63e847091fe05fd71d21bc349a320076ce9336b85b823ca5cd849dced70faec82d6cbdd4f25f822426a5c1ddb081400b885185e537008248dfc89905d0c132d05c43730cf746aca40e349801c1cbca3c439902bd5c31bb8c8bc9539dcd815d977a86d79f49122e1d526623c6c7f679158f10d5e71cc4efa40582814e51ce706bc29c413710423a378b65c50f67d5f84f6ddbcb8dbe4b72cf31fc23ebaa62e3a9afb05a43665679965f13e979b358ee2d7ec54312186d2d773edb61b6d84536f636d63bf3c206c40b29e7d7b638556d56956b9bd7fa8b2cde672836463e32ba855baec1b8f421caba3eb73956362d3d3ba848d36bee1418486058db34af1e43b6d8f7e4c233d3fec40dce2aa541836b033715484399c9fb8a258bd2d1ccea717e2578440588c3b3c022865b0f3d650c2c153741681c048e81d51eef79850ac3b12d81e48fc2c658423549224992374f3c63752e908569c21eada3b4d506f4a225fdd4059b6b2a088f4ca63d4cbc9099e5da26c4137e27f24a1380138ac927de0e2496244b05d925508490a0f3122706a66a5890cfcfec433e547b6672ca75fd7b8c54799a71a54416ec31053e9759d4982f725c656e280e8ae2210028a56a2623653756f442bb58a5b800dc6ed8d9dbc33ef128ba5504896bb3c953b6acd29692c876cb351da2fa4f9edf4b4d8b2fa8d33ea05ae50eec813490a45e1d29f399cf4540f61c7a1d15227b4f20c2304663e9ed4104f070f18c79244e371db9e55ded3dd06593dc5a0164856a59c287eea089c649bcbc2456988cb6c81e2590b454c18b2fefa46776a2bfe3ceb763a973288198314a796e162a64326c2c6531ca0354efec2768fac208f8fd9ea818c876a91bb603249cf8855f172f3796b0ed36ced51b3afc52cb4364bf3e7ab1e96c61bf97bdafb2ea469cd307a33b1400f5c358684369e3925e68850fde5ca0783e73a3703c536fe69a20693f881e8097010740b5984eca237018868241335d69e4ee90fac82e21b833c209359edb13e0067728f86398780d4ed44b2c36e77eab067b0df5097614df9becf65ff66c9b6c625dd31ead6381a65477ffa7bf965869d34567d1284e7306e28340c88ebc9d23d90ab559d3f9675520c923e40cd76286ffd4c0fff1a81070b0ca72587d379b9d4b376cc6402057ca1fc63f3c6a179852fba24841224cef2d6fd4480a189f0f667e654b6b6f79f0443c920cfaa6eebc8ff3e3d3ec95eca273ffd4ab5709ef855c1f5ceadc7f343b78a80e844105bfd3e939eef5f48a4a4746022e4b4e125adb9379570d01f1b279a37506c9241935671935d972f8aa6e8de6abe9f39bcbacdffb4537287ccfe2ec1cc5d7cdd7797f13f579febb894ccfe90710ebec7b03d0117cd4884499c0a8353d798be21c2de1198b1e2c2d973078c2cfad857bcff7e61b0a3868282da237bb164773bdd4aad7fb461bfd9b86102d5d95eb9c4f47c3324a77e3be4c8e2dffea73a42e7dcef394e58920ed979ba3e9fd625721cd48d89f3e41e5924409c4e8e592de1096e51a0035fd50d299fff2df11e8a8982d6f3852108956cd361bd33b8c5ec4000d08126f6d51dffd60bf2ac759fc08f5fed98be04660362e0e7d6a054dd09e491f2cd1387fea8c97fbe459fecc170b6fe67b3ec914b571038f8f56ef99d9eea11b4593bf4d166e3cce797d95848c0e1f028722088b4572d0d34909cac3c6b6e7b22510ffae5a65d172f95cc53ae8078aebd8733cec767d6100eeec68ed3fe28028684dff9a785c4eda7a55438607139f79d87dc4a90093d32edb6927a416f527149d26de6fb9d9a2d27e6e4f4c062ca2cbe9b3da45bd4b4d0042f4d7a74b72e244c0e82b4fbb9233a60717af280eee76fb7c5949c7dea22e6b3e0c76b71e1cca120f01a4dc39ee07135ce4c500899b553a728dc884fd4b443ae6f3383edc7419440b892d97764f2484b5814345d8659968cce248d63ffc7ac37c976b08df61306a8d808a02145f0b0b5a0b21d05bbaf92af3c84f8c96324dd9f3d0b44ef655fb8f30d4b6e1ed3576b9ded62a0e47714af2a6ee3590c6b8988294e0a1faf440374ef577c1f38404903e931a4b577dda9b3cc40886db01afdaabf5c0c840968a32766ef9b15bb0967068a78d83f1773d9c911d2a25b1e103e65fb36040160b8fdbcd39bf803d73f420f073d358769d50e838f8c4f9e733dd6441bda47aa2a9e71acf057a550fef1bb9e5e98b668548a293f8be83ab98ff42658f3ea7aa4b654c4939ec2fd9fd96e1b2ce0e333ab3e120a993f4fe276610493e22899294911e90a2950ef3bef2feab4056d8b1510673a060ad105477ea29f6983c67fa137fb22063f49087f4113db913d09da0a140502c97b123fd4ff53f6893a0491f5bfd701f1981e011f53e0d0b3e25018d8538f1096e8c588ec4605dcea053065b8bbeed085e22feeb8a7cbf835aaf55e00b196152184650aa80f20e6a3a94fba121f0a9cef9c3f88091ff28ce322e6154afcd59a7cb688d1a9b0d6411c4d6c1d1ea1e7b1567cc78092e4ef15ac41b6c768c950a0397e2e312bc09a6a1f464e1c35e5d40b809a870fe6eea6bb1d0bc3c94fa894d6b28bcdb472003000c0714585e788ddeaac91c8e89a9c1cd1b0ed26f2db3c5539a075e5659423ade8f1e3cf08c2869838ecaa9e74fae1dc1a553673b4746da4eb35a4779058b94beb58361f3e837e34953cd050b08b670f9bca33214218a7c3e651ac6b4e1f1cd20e2d42681aca4903d3e4a4bb83ca723ef5fac34c53300a93cc043b78f6925fb3c187914e135e957a690a8ba1882f0193268923675d2c968be1b1b94ac4d698a48228dbbea57f386a748721073a191d8dc5103304fc5d13ecc20869e9b72c751fad6ad83802d7a1a0fd344aa3223683fd103eb4bdea9e3578eb22fb4cbfc0da466f395e445315de39cb5e8213970796c0bb9160c78bcb8a6a3de2547bd3be68f068f2eec3a1aa6fc1a2cb9bae43a21e517430461074b62b1d56a5c0ad9069dd46cc99604e3821a7edced163e5da4765a77d01b1bbd0a84668542a946ee946e2ce9ccdbd697536cf5473462e8a19280192f00d92dd12992f42cc3266c015129575a94d7ae54a3b2fc6b817c9fa604d1e7d69416b4908131ba0d592b1678b6d4cc4c1a46881fd7340411dba16e1e4f64f368035254d3aa106b09044129eaa4c4112dfd8d5c336d8b884524796cc00cedf1b541395764989caaeb6a81405982dcfe8c92dce1fb1617556c7582a208c0ecfb000000000000000000000000000000000000000000000000000006080d12191d

GodCypher

Binding: Both layers are signed by the printer that sealed this timestamp, together with its digest.
Countersign: CountersignedNot sealed
Window: USGS day feed, published by 2026-11-03 21:53:08.000 UTC, 205 earthquakes, this one among them
Window source: https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson
Window digest: fe9dc272…b56e2f34
Countersigned by: zk13str_b4c421607b749197aff78f3edb58ce087a7a16b6_16a1 · the printer
Checked here: the signature, the digest it is over and the window digest all verify on this server. The window itself was not re-fetched here.
What it proves: this countersigned timestamp did not exist before 2026-11-03 20:11:58.520 UTC, when the eighth-newest earthquake in the window happened, once a re-fetch of the window confirms it. Both routes rest the bound on the eight newest earthquakes, never on one, so it is looser by design than the newest; a re-fetch from the permanent catalogue, after the feed has moved on, confirms the eighth-newest it matches, less five seconds. The window’s publication is shown above as “published” and is not a proven bound. A lower bound only.
Sealed evidence: Not sealed: GodCypher parties not configured

What this page checks, it checks on this server. The full check is node scripts/jord.mjs verify on your own machine, with --refetch to re-fetch the window.

The upper bound is not GodCypher’s: it is the Roughtime signed time above, the national laboratories’ judgement of the printer’s clock, and the chain anchor once one is submitted. How a GodCypher timestamp works.

Anchor

Pending Not anchored yet. Anchoring timestamps on the chain is not live; when it is, this line names the transaction and the block that carry this timestamp’s digest. Until then the chain holds none of it, and the page says so rather than pointing at a block that does not hold it.

Check it yourself

Read the timestamp as data. /api/timestamps/5359d27b6be4b0a2c2c36d2e766112fc7ed4b9eea615b8da21f2716bcd6b5c65 is this page as JSON: every value the digest covers, as it was digested, and the GodCypher layers beside it.
Recompute the digest, check the seal and re-fetch the countersign window on your own machine: save that JSON as timestamp.json and run the SourceLess code over it:
```
node scripts/jord.mjs verify timestamp.json --refetch
```
Each layer is reported on its own. A window the verifier could not reach is reported as not confirmed, never as a pass.
Check each observatory at its source. The addresses in the evidence table are printed as text for you to open yourself; this page links to no other site. An observatory may revise its values later, by a little.
Once it is anchored, open its transaction and check that it carries the digest shown on every timestamp.

All GodCypher timestamps