← previous blocknext block →recent activity
Analyzing
Block #106,235,169
22 transactions · 21 stateful · 2026-09-19 17:20:41 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,235,169 · 22 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
1w02w13w06w07w18w29w210w313w416w517w618w719w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf00e711b…c539
0x34b655…2a6f
12 touches
15 conflicts
0x800ca1b7…14b5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x2257be8c…d019
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xf00e711b37…00c539
Audit this contract →
← previous block·next block →recent activity