← previous blocknext block →recent activity
Analyzing
Block #106,389,709
25 transactions · 20 stateful · 2026-09-20 06:18:23 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,389,709 · 25 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
1w02w04w07w18w211w312w113w216w217w320w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 conflicts
0xfbc95f8d…95ab
0x34b655…2a6f
10 touches
10 conflicts
0x7cee389f…adef
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity