← previous blocknext block →recent activity
Analyzing
Block #106,389,365
36 transactions · 31 stateful · 2026-09-20 06:16:39 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.86
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,389,365 · 36 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
1w02w13w24w35w06w17w218w324w327w428w530w631w735w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d5b40dc…27c9
0x34b655…2a6f
14 touches
21 conflicts
0x1c840894…764a
0x34b655…2a6f
14 touches
21 conflicts
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
8 touches
6 conflicts
0x46b5b1f9…9231
0xd32edf…ff58
7 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 0x2d5b40dcdb…a727c9
Audit this contract →
← previous block·next block →recent activity