← previous blocknext block →recent activity
Analyzing
Block #106,389,212
31 transactions · 27 stateful · 2026-09-20 06:15:53 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.97
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,389,212 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w110w211w313w214w215w319w320w421w522w624w625w726w827w930w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca92d069…9633
0x34b655…2a6f
14 touches
21 conflicts
0x41869112…4809
0x34b655…2a6f
12 touches
15 conflicts
0xc8cb0701…3926
0x34b655…2a6f
10 touches
10 conflicts
0x48203298…65cb
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0xca92d06981…369633
Audit this contract →
← previous block·next block →recent activity