← previous blocknext block →recent activity
Analyzing
Block #106,952,360
13 transactions · 13 stateful · 2026-09-22 05:31:17 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,952,360 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x7b92b5ef…9f17
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x67287ef9…2d07
0x34b655…2a6f
4 touches
1 conflict
0x148c2efc…4410
0x34b655…2a6f
4 touches
1 conflict
0xb21571f6…8741
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
2 touches
0 conflicts
0x60c7a9f8…9886
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x9375a764b5…f0dca1
Audit this contract →
← previous block·next block →recent activity