SASEUL Weekly Network Log #1, Sep 27 to Oct 3, Hashrate Dropped and Then Climbed Back

How did the SASEUL network move this week?
Total calculating speed fell 34%, then climbed back 26%
6.88 trillion
Sep 27, per second
4.54 trillion
Oct 1, lowest this week
5.74 trillion
Oct 3, per second
From September 27 to October 3, 2026, SASEUL's total calculating speed went down and then came back up. It fell 34%, from 6.88 trillion calculations a second to 4.54 trillion on October 1, and reached 5.74 trillion on October 3. That's still about 17% below September 27.
This post has two parts. The first is about the whole SASEUL network and follows the official explorer's numbers. The second is about one small mining pool inside it, with the pool site's numbers kept separate.
As calculating speed changed, the pace of new blocks changed with it. The number of mining computers stayed about the same, at 43 to 46. Why it dropped and then rose couldn't be found in public data. All times below are Korea time (KST).
Calculating speed hit its low on October 1 and came back by the 3rd
Hashrate (guesses per second) shows the combined power of everyone mining SASEUL coin. The numbers below were read off the official explorer's front page and statistics screen each day. Calculating speed was worked out by dividing the explorer's difficulty by 60 seconds, so it's an average, not a direct measurement, and it moves together with difficulty (more below). The same value shows up in the NETWORK box on the pool site's front page.
| Recorded at (KST) | Total calculating speed (per second) | Explorer difficulty (T is explained below) | Mining / up-to-date computers |
|---|---|---|---|
| Sep 27, 9:46 | 6.88 trillion | 375.57T | 46 / 74 |
| Sep 30, 12:58 | 5.02 trillion | 274T | 45 / 62 |
| Oct 1, 7:11 | 4.54 trillion | 247T | 44 / 60 |
| Oct 2, 7:11 | 4.99 trillion | 272T | 44 / 60 |
| Oct 3, 7:11 | 5.74 trillion | 312T | 44 / 61 |
In terms of a card doing about 860 MH/s (MH/s means millions of guesses per second, so about 860 million per second), 5.74 trillion is the power of roughly 6,700 cards put together. On September 27 it was roughly 8,000.
There's no record for September 28 and 29. So I can't say October 1 was really the lowest day. It's the lowest of the days I recorded.
This speed is worked backward from difficulty
The NETWORK value on the pool site's front page matches difficulty (the average number of guesses it takes to find one block) divided by 60 seconds. On October 3, the explorer's statistics screen showed a difficulty of 344,101,475,117,601. Divide that by 60 and you get about 5.74 trillion a second.
That means this number isn't measured directly. It's an estimate, an average worked out from difficulty, so the two are the same number shown another way and move together. It only changes when difficulty changes. Even if mining power jumps suddenly, it shows up late, after difficulty catches up. How difficulty and calculating speed connect is explained in what SASEUL difficulty means.
The explorer showed "~5.22 TH/s" the same day. The T in the table and the TH/s on the explorer count in units of 1,024 × 1,024 × 1,024 × 1,024 (about 1.1 trillion) instead of one trillion, so the number just looks smaller. It's the same value.
About 67 seconds per block while power dropped, about 52 to 54 while it rose
A block (one page of the record book) is supposed to come once a minute, 1,440 a day. I worked out the real gap from the difference in the mining record page (resource block) numbers I wrote down.
| Period (KST) | Blocks added | Average gap per block |
|---|---|---|
| Sep 27 9:46 → Oct 1 7:11 (about 93 hours) | 4,991 | about 67 sec |
| Oct 1 7:11 → Oct 2 7:11 (24 hours) | 1,589 | about 54 sec |
| Oct 2 7:11 → Oct 3 7:11 (24 hours) | 1,658 | about 52 sec |
While power was dropping, blocks came slower than the target. While it was coming back, they came faster. Between October 2 and 3, there were about 15% more than 1,440.
That's what you'd expect from proof of work in general. More mining power means answers come faster, and once difficulty rises to match, the gap drifts back toward one minute.
Mining computers stayed at about 43 to 46
The first number in the Nodes box on the explorer's front page is the nodes (computers that each hold a copy of the record book) mining right now. This week it was between 43 and 46. The second number (computers fully synced to the latest record book) went from 74 on September 27 to 60 to 62 this week.
These numbers change within minutes. Even on September 27, it flipped between 74 and 63. So the computer count alone can't explain why calculating speed changed.
One pool mostly had under 1% of the total, and its numbers swung a lot
From here on, these aren't numbers for all of SASEUL. They're for one pool site (saseulmine.com). The site itself says it's an unofficial community pool with no ties to the SASEUL project. I read its front page each day.
| Recorded at (KST) | Pool calculating speed (per second) | Share of total | Pool's mining computers | Blocks the pool found (total) |
|---|---|---|---|---|
| Sep 27, 9:46 | 41.54 GH/s | 0.6% | 6 | 76 |
| Sep 30, 12:58 | 29.3 GH/s | 0.6% | 6 | 88 |
| Oct 1, 7:11 | 24.7 GH/s | 0.5% | 7 | 90 |
| Oct 2, 7:11 | 29.25 GH/s | 0.6% | 8 | 98 |
| Oct 3, 7:11 | 43.33 GH/s | 0.8% | 7 | 108 |
In the five readings in the table, the pool's share was 0.5 to 0.8%. The pool's calculating speed moves a lot even within a day. At 11:43 pm on October 3, it showed 18.76 GH/s and a 0.3% share. With only 6 to 10 computers, just one or two switching on or off makes the number jump.
So you can't read the trend for all of SASEUL from the pool's numbers. Blocks found by the pool went up by 32 from September 27 to 7:11 on October 3. Over the same period, 8,239 mining blocks were added network-wide. Counting by blocks found, the pool's share was around 0.4%.
So what should you do? Look at the week, not the day
- Daily numbers pile up in the network record. If one day drops a lot, check the weekly trend too
- To see today's value yourself, look at Latest Difficulty on the official explorer's statistics screen and work it out the same way (divide by 60 seconds)
- To see whether blocks are still coming, the method in how to check if SASEUL blocks have stalled takes a minute
SASEUL's basic numbers are in SASEUL basic facts.
Sources
- saseulmine.com front page (NETWORK box, plus the pool's own calculating speed, computer count and blocks found) · checked 2026-09-27 09:46, 09-30 12:58, 10-01 07:11, 10-02 07:11, 10-03 07:11 KST, extra check 10-03 23:43 KST
- Official SASEUL explorer front page (Resource Blocks, Nodes, Difficulty) · checked at the same times, 10-03 07:11 KST Resource Blocks 2,332,305 · Nodes 44 / 61 · Difficulty 312T
- Official SASEUL explorer · Statistics (Difficulty 312.96 T ~5.22 TH/s, Latest Difficulty 344,101,475,117,601) · checked 2026-10-03 07:11 KST
- Daily records are in this blog's network record (values read off the saseulmine.com and explorer.saseul.com front pages that day)
I hold SL. The numbers above were read by hand off saseulmine.com and the official SASEUL explorer's front page and statistics screen, day by day, from September 27 to October 3, 2026.