← previous blocknext block →recent activity
Analyzing
Block #108,498,626
20 transactions · 19 stateful · 2026-09-27 15:16:23 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,498,626 · 20 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
2w03w16w07w18w29w210w311w412w113w314w215w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
8 touches
6 conflicts
0xf1c8fb51…c035
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x451469f0…5c65
0x34b655…2a6f
6 touches
3 conflicts
0x5bf26b70…28d1
0x34b655…2a6f
6 touches
3 conflicts
0xb7b446d2…2006
0x34b655…2a6f
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)
6 conflicts on slot 0x0000000000…00001c
Audit this contract →
← previous block·next block →recent activity