News
19.07.2026
New design! The explorer got a fresh, hand made look. Bootstrap and all other
external CDN dependencies are gone, the whole UI now runs on plain CSS and vanilla
JavaScript. The page is lighter, loads faster and the PHP backend was cleaned up too.
Also new: nickname suggestions in search, rows per page selector, freshness dot next
to every table and keyboard shortcuts (press / to search, Esc to clear).
07.02.2026
Upgrade/degrade. After 07.02.2026 this data is shared by a new server based on
Intel Pentium Silver N6000 and 8 GB RAM... (previous is i5-7500T, above 10 GB RAM per
container with elastic) so nice and powerful upgrade xd. Elasticsearch has now 2 GB of
RAM allocated. After this update, newest values can show a little slower, especially
grouped values (accounts).
What is this?
This explorer retrieves blockchain-related data from server.duinocoin.com
at regular intervals. Please note that the data may not always reflect real-time updates
and not including all data exists in DuinoCoin.
This uwu project is only preview explorer for training my networking configuration
(especially port forwarding and security) and elasticsearch usage. I just want creating
similar blockchain explorer like bitcoin and this project allow me to realize this.
All data is updated regular every several hours/minutes for prevent overuse servers and
make this project easily to programming.
Technologies used
- PHP: Handles server-side logic, interacts with the database, and
generates API responses for the explorer.
- MariaDB: Stores structured data for accounts, transactions, and
other blockchain-related records efficiently.
- Elasticsearch: Powers fast and flexible search capabilities,
enabling users to find specific transactions, blocks, or accounts instantly.
- Vanilla JS and custom CSS: The whole UI is hand made, with no
frameworks and no external dependencies, so the page stays small and fast.
- ETL (Extract, Transform, Load): This is not technology, but
important pattern allow converts duco data into structured formats suitable for
database and Elasticsearch ingestion.
Together, these technologies enable the explorer to present data in a user-friendly
manner while maintaining speed and accuracy.
Some data might be incorrect, eg. dates or identifiers. Because i use
own dates when i get this data. I use sometimes duco dates, but not always.