← previous blocknext block →recent activity
Analyzing
Block #106,235,567
22 transactions · 22 stateful · 2026-09-19 17:22:41 UTC
Parallelism
55/100
Blocked
64%
Avg conflicts / tx
2.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,235,567 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w19w210w311w412w513w614w715w816w921w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f9a70…b139
0x34b655…2a6f
12 touches
15 conflicts
0x81e786d2…ca8c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x25957369…c648
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
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 0x160f9a70df…14b139
Audit this contract →
← previous block·next block →recent activity