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

· Updated · Holder guide

#DifficultyAndGPU

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

Drawn from this blog's network log (values read daily from the official explorer and saseulmine.com, September 27 to October 16, 2026). Arrows show the order of events, and the darker box is the result. TH/s is a speed of one trillion calculations per second. Calculating speed is difficulty divided by 60 seconds, so it moves in the same shape as difficulty. T is the explorer's difficulty unit, about 1.1 trillion tries.

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)

9/27 · 6.88 TH/s 6.88 9/27 9/30 · 5.02 TH/s 5.02 9/30 10/1 · 4.54 TH/s 4.54 10/1 10/2 · 4.99 TH/s 4.99 10/2 10/3 · 5.74 TH/s 5.74 10/3 10/4 · 6.17 TH/s 6.17 10/4 10/11 · 5.69 TH/s 5.69 10/11 10/12 · 5.4 TH/s 5.4 10/12 10/13 · 4.26 TH/s 4.26 10/13 10/14 · 4.26 TH/s 4.26 10/14 10/15 · 3.41 TH/s 3.41 10/15 10/16 · 3.18 TH/s 3.18 10/16
Each bar is one recorded day. September 28 and 29 and October 5 to 10 have no record, so they are skipped, and the darker bars are the first (9/27) and last (10/16) records. It is the explorer's difficulty divided by 60 seconds (standard units). Source: this blog's network log (data/snapshots.jsonl).

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

  1. Check calculating speed and difficulty by date in this blog's network log, a week at a time
  2. 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
  3. If something big changes on the network, check the official Telegram notices first
  4. 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


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).

Questions after reading this

Leave a question you want answered. Useful ones are added to this post with an answer. Please do not include your name, contact details, wallet address or recovery phrase.