← previous blocknext block →recent activity
Analyzing
Block #106,235,136
22 transactions · 19 stateful · 2026-09-19 17:20:31 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,235,136 · 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
1w02w15w16w27w19w010w117w218w319w420w521w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a4230da…3359
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf00e711b…c539
0x34b655…2a6f
6 touches
3 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
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
10 conflicts on slot 0x6a4230da18…573359
Audit this contract →
← previous block·next block →recent activity