← previous blocknext block →recent activity
Analyzing
Block #106,199,378
25 transactions · 25 stateful · 2026-09-19 14:20:27 UTC
Parallelism
60/100
Blocked
52%
Avg conflicts / tx
1.92
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,199,378 · 25 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
1w02w13w25w09w110w011w112w213w314w415w517w618w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cf3eb0f…06c5
0x34b655…2a6f
14 touches
21 conflicts
0x9b4a1a55…66db
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x90d24713…b88e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x310a7246…2dcb
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
21 conflicts on slot 0x7cf3eb0f68…8806c5
Audit this contract →
← previous block·next block →recent activity