← previous blocknext block →recent activity
Analyzing
Block #106,408,403
22 transactions · 19 stateful · 2026-09-20 07:52:27 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,408,403 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w110w113w214w315w416w517w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x228da3f5…c2bf
0x34b655…2a6f
12 touches
15 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0x54563e2b…7469
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity