← previous blocknext block →recent activity
Analyzing
Block #106,235,555
36 transactions · 32 stateful · 2026-09-19 17:22:37 UTC
Parallelism
75/100
Blocked
63%
Avg conflicts / tx
1.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,235,555 · 36 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w17w19w210w216w220w221w322w424w126w427w528w630w834w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68a3da5a…f84c
0x34b655…2a6f
16 touches
28 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
12 touches
15 conflicts
0x86cea35b…bdff
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x5780865a…35f5
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x8fc9c747…80f8
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 0x68a3da5a5b…36f84c
Audit this contract →
← previous block·next block →recent activity