← previous blocknext block →recent activity
Analyzing
Block #106,959,157
17 transactions · 17 stateful · 2026-09-22 06:05:30 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,959,157 · 17 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
3w04w15w27w08w111w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0x51aa664e…d3b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
0xa140ac77…1f0c
0x34b655…2a6f
6 touches
3 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
6 touches
3 conflicts
0xc11f059c…1eb9
0x34b655…2a6f
6 touches
3 conflicts
0xc5d75bd2…1afb
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
6 conflicts on slot 0x3243e72f11…1d1f6d
Audit this contract →
← previous block·next block →recent activity