← previous blocknext block →recent activity
Analyzing
Block #108,564,988
18 transactions · 18 stateful · 2026-09-27 20:50:38 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,564,988 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w211w012w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0xdc2735d2…5295
0xd32edf…ff58
5 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
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)
3 conflicts on slot 0x0000000000…00001e
Audit this contract →
← previous block·next block →recent activity