← previous blocknext block →recent activity
Analyzing
Block #106,575,710
24 transactions · 23 stateful · 2026-09-20 21:54:32 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,575,710 · 24 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
1w02w03w14w07w19w010w211w313w114w415w416w517w618w721w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4dfe994…e3d0
0x34b655…2a6f
14 touches
21 conflicts
0x110a3804…f842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x33387c27…44cc
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
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
21 conflicts on slot 0xa4dfe994b8…9ce3d0
Audit this contract →
← previous block·next block →recent activity