← previous blocknext block →recent activity
Analyzing
Block #106,931,001
24 transactions · 23 stateful · 2026-09-22 03:43:46 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,931,001 · 24 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
2w03w14w25w36w48w29w310w411w512w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
14 touches
21 conflicts
0xd4230a60…bd13
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xf8d9af5e…eba6
0x34b655…2a6f
10 touches
10 conflicts
0x16eed475…62dc
0x34b655…2a6f
10 touches
10 conflicts
0xc904e126…fcf0
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
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
21 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity