SASEUL Blocks Keep Coming Even When Miners Drop Off, Based on 3 Weeks of Records

SASEUL difficulty and calculating speed over 3 weeks
Blocks kept coming even as miners dropped off
Some miners seem to have left
Calculating speed Sept 27: 6.88 → Oct 16: 3.18 TH/s
Difficulty comes down too
Difficulty 375.57T → 173T. Calculating speed is an average worked out from difficulty, so the two move together
Blocks keep coming
About one every 63 seconds over 3 weeks
Even though some of the people who were mining seem to have left, SASEUL blocks kept coming. Difficulty (how hard the puzzle for one page of the record book is) came down along with them, so blocks kept arriving close to the 60-second target.
The total calculating speed (hashrate) shown on the explorer isn't measured directly. It's an estimate, an average worked out by dividing difficulty by 60 seconds. So calculating speed isn't a separate signal from difficulty. It's the same number shown another way (what difficulty means). This post sums up the difficulty and calculating speed this blog recorded daily from September 27 to October 16.
Difficulty and calculating speed came down together over 3 weeks
Every day I copy numbers from the official explorer into the network log. Total hashrate (how many guesses per second; TH/s means one trillion per second) was 6.88 TH/s on September 27. The early-morning reading on October 16 was 3.18 TH/s. It's worked out from difficulty, so it came down in the same shape as difficulty (375.57T to 173T).
SASEUL total calculating speed (TH/s, worked out from difficulty, logged days only)
Using the latest difficulty on the explorer's statistics screen at 12:39 pm the same day, it works out to about 3.27 TH/s. That screen counts in units of 1,024, so the same value shows there as "~2.97 TH/s". Every TH/s number in this post uses ordinary units of 1,000. Only the T in the difficulty numbers (375.57T, 173T) is the explorer's unit (about 1.1 trillion).
I don't know who left. The number of nodes (computers holding a copy of the record book) mining was 46 on September 27 and 44 on October 16, almost unchanged. Public data can't tell whether a big miner left or many people turned off some machines.
Meanwhile, blocks came about every 63 seconds on average
I worked out the gap from the difference in mining block numbers I'd logged. From 9:46 am on September 27 to 12:39 pm on October 16, 26,253 pages piled up. That's about 63 seconds a page on average.
| Period | Average gap per page |
|---|---|
| September 27 → October 16 (about 19 days) | about 63 sec |
| October 12 → October 14 (while calculating speed was coming down fast) | about 75 to 77 sec |
| October 15 → October 16 | about 59 sec |
In the few days before difficulty came down, the gap got longer, then came back toward one minute once difficulty came down. Earlier, from September 15 to October 4, calculating speed also came down from 9.88 to 5.82 TH/s, but the average was about 62 seconds (from the fact-check record of the home mining post).
Blocks keep coming because of difficulty and validator seats
When fewer people mine, answers come later. Then difficulty goes down until answers come about once a minute again. Total calculating speed is this difficulty divided by 60 seconds, so the two move together. Explorer difficulty went from 375.57T on September 27 down to 173T on October 16. There's more on what it means in what difficulty means.
The record book for transactions is a separate one. The official docs say a node that succeeds at mining serves as a validator for a while. There are 9 seats, and a page of the transaction record book goes through once 6 seats sign (the two-chain structure post).
What changes when calculating speed comes down: the power needed to hold the record book
This is the general idea behind proof of work. The Bitcoin white paper explains that as long as the honest side holds a majority of the calculating power, it outpaces an attacker. So as total calculating speed gets smaller, the size of that majority gets smaller too. On the explorer at 12:39 pm on October 16, the 9 validator seats were held by 6 different addresses.
Individuals who keep mining get a bigger share of the same amount
Your share is your calculating speed divided by the total calculating speed. One card doing about 860 MH/s (860 million calculations per second) was about 0.0125% of the total on September 27. Going by the early morning of October 16, it's about 0.027%. Total calculating speed is an average worked out from difficulty, so the real share can differ a little from these numbers.
So the same card gets roughly twice the share. For the opposite story, how shares shrink when more individuals mine, see what changes if more people mine at home.
So what should you do? Watch the trend and official notices, not one day's number
- Check calculating speed and difficulty by date in this blog's network log, a week at a time
- To see whether the record book has really stopped, compare the time on the top block under Latest Resource Blocks on the front page of the official explorer with the current time. The Resource Interval next to it is the gap between the last two pages. How to do it is in how to check if blocks have stalled
- If something big changes on the network, check the official Telegram notices first
- If you're mining, rerun your power cost with how to work out mining electricity cost. A bigger share doesn't change your electricity bill
SASEUL's basic numbers are in SASEUL basic facts.
Sources
- This blog's network log (data/snapshots.jsonl: values read daily from the saseulmine.com NETWORK box and the official explorer front page. September 27 9:46 am: 6.88 TH/s · 375.57T · nodes 46/74 (the first number is nodes mining now, the second is nodes synced to the latest record book) · mining block #2,324,067; October 16 5:31 am: 3.18 TH/s · 173T · 44/61 · #2,349,871)
- Official SASEUL explorer · Statistics (Difficulty 178.33 T ~2.97 TH/s, Latest Difficulty 196,080,521,090,615, Total Resource Blocks 2,350,320, 6 different addresses across 9 validator seats) · checked 2026-10-16 12:39 KST
- Official SASEUL explorer front page (Nodes 44 / 61, Difficulty 178T, Resource Interval) · checked 2026-10-16 12:41 KST
- Official SASEUL docs · Node Overview (a node that succeeds at mining serves as a validator for a set period; the resource chain handles validator selection and mining) · checked 2026-10-16
- Official SASEUL Telegram notices (the last notice when checked on 2026-10-16 was the 2026-09-15 pool introduction) · checked 2026-10-16
- CoinMarketCap · About SASEUL (60-second target for the mining record book, 6 of 9 seats sign) · the project's own description, checked 2026-10-04 (recorded in the home mining post)
- Bitcoin white paper "Bitcoin: A Peer-to-Peer Electronic Cash System" (majority of calculating power, difficulty rises if blocks come too fast) · checked 2026-10-04 (recorded in the same post)
- Average gap for September 15 to October 4: mining block #2,307,600 (2026-09-15 12:06:36) to #2,334,418 (2026-10-04 19:22:18), 26,818 pages ≈ 62.2 sec (data/factcheck/2026-10-12-개인-채굴-늘면-달라지는-것.json)
- Math: average gap = September 27 9:46:46 am to October 16 12:39:35 pm (about 458.9 hours) ÷ 26,253 pages ≈ 62.9 sec. October 12 5:39 am → 13th 5:31 am, 1,122 pages ≈ 76.6 sec; 13th → 14th, 1,158 pages ≈ 74.6 sec; 15th → 16th, 1,472 pages ≈ 58.7 sec. Midday value = 196,080,521,090,615 ÷ 60 ≈ 3.27 TH/s. One card's share = 0.86 ÷ 6,880 ≈ 0.0125%, 0.86 ÷ 3,180 ≈ 0.027%
I hold SL. The numbers come from the network log this blog keeps every day (September 27 to October 16), and from the official explorer, official docs and official notices I opened myself between 12:39 and 12:41 pm on October 16, 2026 (KST).