← previous blocknext block →recent activity
Analyzing
Block #106,930,953
40 transactions · 40 stateful · 2026-09-22 03:43:32 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
1.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,930,953 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w08w09w110w011w112w213w314w415w516w117w219w220w321w422w523w624w125w326w427w530w234w235w136w437w638w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
14 touches
21 conflicts
0xf8d9af5e…eba6
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xab981df1…2941
0x34b655…2a6f
12 touches
15 conflicts
0xd4230a60…bd13
0x34b655…2a6f
12 touches
15 conflicts
0x16eed475…62dc
0x34b655…2a6f
10 touches
10 conflicts
0xb8185207…6ccc
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 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 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity