← previous blocknext block →recent activity
Analyzing
Block #106,393,071
26 transactions · 24 stateful · 2026-09-20 06:35:19 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,393,071 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w18w213w316w417w518w620w721w822w923w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa384061e…9f51
0x34b655…2a6f
16 touches
28 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x000bde1a…e123
0x34b655…2a6f
10 touches
10 conflicts
0x8f63f383…6eda
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x2c2761c0…476e
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
28 conflicts on slot 0xa384061e1d…549f51
Audit this contract →
← previous block·next block →recent activity