← previous blocknext block →recent activity
Analyzing
Block #106,188,580
26 transactions · 25 stateful · 2026-09-19 13:26:06 UTC
Parallelism
69/100
Blocked
52%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,188,580 · 26 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
1w02w13w04w15w214w315w416w417w518w623w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892587dc…c0ff
0x34b655…2a6f
14 touches
21 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0x9167c873…748f
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 0x892587dc9c…f8c0ff
Audit this contract →
← previous block·next block →recent activity