← previous blocknext block →recent activity
Analyzing
Block #106,192,353
19 transactions · 18 stateful · 2026-09-19 13:45:06 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,192,353 · 19 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
2w03w14w15w29w010w111w012w114w315w416w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d9f22d…e99f
0x34b655…2a6f
10 touches
10 conflicts
0x78b46e16…e0cb
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
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 0xf5d9f22d0a…65e99f
Audit this contract →
← previous block·next block →recent activity