← previous blocknext block →recent activity
Analyzing
Block #108,641,172
24 transactions · 22 stateful · 2026-09-28 03:14:14 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,641,172 · 24 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
3w04w15w210w011w112w213w317w419w523w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x5e606da6…3def
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
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…000012
Audit this contract →
← previous block·next block →recent activity