← previous blocknext block →recent activity
Analyzing
Block #106,235,171
24 transactions · 19 stateful · 2026-09-19 17:20:41 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,235,171 · 24 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
3w07w010w111w012w213w316w317w018w119w420w121w522w123w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf00e711b…c539
0x34b655…2a6f
12 touches
15 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe47b6989…c993
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x800ca1b7…14b5
0x34b655…2a6f
4 touches
1 conflict
0xab621973…cc16
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 0xf00e711b37…00c539
Audit this contract →
← previous block·next block →recent activity