← previous blocknext block →recent activity
Analyzing
Block #106,163,935
25 transactions · 25 stateful · 2026-09-19 11:22:05 UTC
Parallelism
76/100
Blocked
28%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,163,935 · 25 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
1w02w13w24w35w010w011w114w123w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xb58ed141…c32e
0x34b655…2a6f
8 touches
6 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0xbb57ce7f…f1f4
0x34b655…2a6f
6 touches
3 conflicts
0xc6bd960b…a00f
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: Perpl
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity