← previous blocknext block →recent activity
Analyzing
Block #106,932,576
25 transactions · 24 stateful · 2026-09-22 03:51:42 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,932,576 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w011w112w214w215w316w417w518w623w424w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
14 touches
21 conflicts
0xc7b7704f…ab36
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
8 touches
6 conflicts
0x14b80268…69ef
0x34b655…2a6f
8 touches
6 conflicts
0x1260550f…1a38
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity