← previous blocknext block →recent activity
Analyzing
Block #106,932,193
21 transactions · 21 stateful · 2026-09-22 03:49:46 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,932,193 · 21 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
6w07w18w09w110w211w012w213w316w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x01dda396…30eb
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x71ecf7c5…8b1e
0x34b655…2a6f
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x85bfd0af…ce96
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
10 conflicts on slot 0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block·next block →recent activity