← previous blocknext block →recent activity
Analyzing
Block #108,010,172
16 transactions · 15 stateful · 2026-09-25 22:18:09 UTC
Parallelism
44/100
Blocked
53%
Avg conflicts / tx
2.25
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,010,172 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001b
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0xca160eca…187d
0xd32edf…ff58
17 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xd5f675a8…9d81
0x34b655…2a6f
2 touches
0 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)
36 conflicts on slot 0x0000000000…00001b
Audit this contract →
← previous block·next block →recent activity