← previous blocknext block →recent activity
Analyzing
Block #106,951,889
18 transactions · 17 stateful · 2026-09-22 05:28:55 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,951,889 · 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
2w03w14w07w18w29w011w312w413w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b8dd4b8…8aa7
0x34b655…2a6f
12 touches
15 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x8f18c248…9da5
0x34b655…2a6f
6 touches
3 conflicts
0xc913404a…a7ce
0x34b655…2a6f
6 touches
3 conflicts
0xebb97840…6a07
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x85c2666e…5acf
0x99c7a7…8bf0
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
15 conflicts on slot 0x7b8dd4b8d4…cc8aa7
Audit this contract →
← previous block·next block →recent activity