← previous blocknext block →recent activity
Analyzing
Block #108,512,531
11 transactions · 11 stateful · 2026-09-27 16:26:23 UTC
Parallelism
36/100
Blocked
55%
Avg conflicts / tx
1.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,512,531 · 11 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001d
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
14 touches
21 conflicts
0x7303135c…b5c7
0xd32edf…ff58
13 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
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)
21 conflicts on slot 0x0000000000…00001d
Audit this contract →
← previous block·next block →recent activity