← previous blocknext block →recent activity
Analyzing
Block #108,494,601
18 transactions · 18 stateful · 2026-09-27 14:56:07 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,494,601 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w07w19w110w211w212w114w315w416w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44d7acbf…e67e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd0cbb207…6aab
0xd32edf…ff58
7 touches
6 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0x19dcf812…44d9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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)
6 conflicts on slot 0x44d7acbfe8…6ce67e
Audit this contract →
← previous block·next block →recent activity