← previous blocknext block →recent activity
Analyzing
Block #106,930,940
20 transactions · 18 stateful · 2026-09-22 03:43:28 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,930,940 · 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
1w02w06w07w18w29w310w411w514w115w117w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x16eed475…62dc
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x721c4bf6…290c
0x34b655…2a6f
4 touches
1 conflict
0x704a8131…bbe8
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 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity