← previous blocknext block →recent activity
Analyzing
Block #106,430,051
23 transactions · 22 stateful · 2026-09-20 09:41:24 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,430,051 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w08w09w111w213w314w415w516w417w618w720w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
8 touches
6 conflicts
0xf3867819…9d3c
0x34b655…2a6f
8 touches
6 conflicts
0x739cf558…6266
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x31c4594c…ede7
0x34b655…2a6f
6 touches
3 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity