5 items
Convert timestamps across configurable timezones and generate copy-ready log query windows for Splunk, Grafana, and CloudWatch. Built by a developer, for developers. DevClock eliminates the mental overhead of timezone conversion during production troubleshooting — just type a timestamp and get your answer. No date pickers. No dropdowns. Just type. —— ⌨️ SMART TIMESTAMP INPUT Paste timestamps in any format directly from your logs or screenshots. DevClock automatically recognises: · Natural language yesterday 4pm · 2 hours ago · last Monday 9am · Time only 3:14pm · 09:00 · 14:30:00 · Relative shorthand -2h · -30m · now-1h · Unix epoch 1718000000 · 1718000000000 · ISO 8601 2024-06-10T14:30:00Z · Syslog Jun 10 14:30:01 · Apache CLF 10/Jun/2024:14:30:01 +0000 · Inline timezone 3:14pm EST · 09:00 AEDT · 2pm BST —— 🌏 SOURCE TIMEZONE TOGGLES Timestamps from screenshots and logs often have no timezone context. Switch the source timezone with one click and instantly re-interpret the same timestamp — no retyping required. —— 🔍 LOG QUERY BUILDER Generate a copy-ready search fragment with a built-in ±1 minute window around your converted time. Paste directly into your query bar. Supports Splunk, Grafana, and CloudWatch out of the box. —— ⚙️ CONFIGURABLE · Set your default target timezone · Customise which timezones appear as quick toggles · Choose your query provider · Switch between 12 and 24 hour display formats —— 🔒 PRIVACY FIRST Runs entirely in your browser. No data is collected, transmitted, or stored outside your own machine. No analytics. No tracking. Ever.
May 6, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.