← previous blocknext block →recent activity
Analyzing
Block #108,494,564
19 transactions · 19 stateful · 2026-09-27 14:55:56 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,494,564 · 19 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
1w02w13w25w36w48w09w210w313w214w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x9f2519e9…1575
0xd32edf…ff58
9 touches
10 conflicts
0xf19ea2f0…c1c3
0x34b655…2a6f
8 touches
6 conflicts
0x2c539d94…b63a
0x34b655…2a6f
6 touches
3 conflicts
0xf7213a75…8d13
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)
10 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity