← previous blocknext block →recent activity
Analyzing
Block #108,503,410
16 transactions · 15 stateful · 2026-09-27 15:40:28 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,503,410 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w510w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
12 touches
15 conflicts
0xe965559c…1f8c
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0xaef7d816…5806
0x34b655…2a6f
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)
15 conflicts on slot 0x0000000000…00001c
Audit this contract →
← previous block·next block →recent activity