← previous blocknext block →recent activity
Analyzing
Block #107,813,037
26 transactions · 24 stateful · 2026-09-25 05:45:50 UTC
Parallelism
77/100
Blocked
63%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,813,037 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w110w211w213w315w016w117w318w119w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58e06bab…34d2
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x33280065…278a
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: ShMonad (shMON)
10 conflicts on slot 0x58e06babf4…8f34d2
Audit this contract →
← previous block·next block →recent activity