← previous blocknext block →recent activity
Analyzing
Block #106,031,602
22 transactions · 21 stateful · 2026-09-19 00:16:06 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,031,602 · 22 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
2w03w14w25w36w08w113w214w315w419w520w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x885efce3…7496
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
8 touches
6 conflicts
0x48828733…fd48
0x34b655…2a6f
8 touches
6 conflicts
0x48b6f2c7…2ef7
0x34b655…2a6f
8 touches
6 conflicts
0x69d2053b…935a
0x34b655…2a6f
8 touches
6 conflicts
0x6d5d1fb5…86a7
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
15 conflicts on slot 0x885efce3b0…367496
Audit this contract →
← previous block·next block →recent activity