← previous blocknext block →recent activity
Analyzing
Block #106,568,886
24 transactions · 23 stateful · 2026-09-20 21:20:12 UTC
Parallelism
63/100
Blocked
65%
Avg conflicts / tx
2.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,568,886 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w210w113w114w216w317w418w519w620w521w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73113592…0f2d
0x34b655…2a6f
12 touches
15 conflicts
0xd9ddc38b…475d
0x34b655…2a6f
12 touches
15 conflicts
0xc1da8f73…484c
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
10 touches
10 conflicts
0x110a3804…f842
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xf1a4a53d…b445
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
15 conflicts on slot 0x73113592d5…100f2d
Audit this contract →
← previous block·next block →recent activity