← previous blocknext block →recent activity
Analyzing
Block #106,430,130
28 transactions · 28 stateful · 2026-09-20 09:41:48 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
2.21
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,430,130 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w415w418w220w521w622w723w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c219c26…3121
0x34b655…2a6f
18 touches
36 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
16 touches
28 conflicts
0x8d175439…fb79
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc8cb0701…3926
0x34b655…2a6f
8 touches
6 conflicts
0x231b7dd8…f465
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
36 conflicts on slot 0x1c219c262b…793121
Audit this contract →
← previous block·next block →recent activity