← previous blocknext block →recent activity
Analyzing
Block #106,916,177
26 transactions · 24 stateful · 2026-09-22 02:29:10 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,916,177 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w19w210w311w113w214w315w416w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x9d4d1acf…db17
0x34b655…2a6f
8 touches
6 conflicts
0x49be85b3…1b66
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x333bf9c2…0730
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
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 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity