← previous blocknext block →recent activity
Analyzing
Block #106,932,207
22 transactions · 20 stateful · 2026-09-22 03:49:50 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,932,207 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w09w110w212w313w414w515w618w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x21679a4f…4dea
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x8fb6bad3…adeb
0x34b655…2a6f
8 touches
6 conflicts
0x251ee419…4404
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 0x810a3aa264…c40227
Audit this contract →
← previous block·next block →recent activity