← previous blocknext block →recent activity
Analyzing
Block #106,951,831
18 transactions · 18 stateful · 2026-09-22 05:28:37 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,951,831 · 18 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
2w03w04w05w16w210w211w212w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5595feb5…9286
0x34b655…2a6f
12 touches
15 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
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
15 conflicts on slot 0x5595feb513…fe9286
Audit this contract →
← previous block·next block →recent activity