← previous blocknext block →recent activity
Analyzing
Block #106,923,865
20 transactions · 18 stateful · 2026-09-22 03:07:51 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,923,865 · 20 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
2w03w16w07w113w214w015w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xea2d1275…76c8
0x34b655…2a6f
6 touches
3 conflicts
0xdc66a2af…568b
0x34b655…2a6f
6 touches
3 conflicts
0xc7839fc4…9649
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity