← previous blocknext block →recent activity
Analyzing
Block #106,422,330
21 transactions · 20 stateful · 2026-09-20 09:02:33 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,422,330 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w37w310w013w014w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe63b3705…28bc
0x34b655…2a6f
12 touches
15 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x3b22ed54…b185
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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 0xe63b3705df…7328bc
Audit this contract →
← previous block·next block →recent activity