← previous blocknext block →recent activity
Analyzing
Block #106,565,053
39 transactions · 35 stateful · 2026-09-20 21:00:54 UTC
Parallelism
80/100
Blocked
49%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,565,053 · 39 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
1w02w13w24w05w06w17w18w210w311w419w322w223w424w325w531w437w638w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0x546fe1d2…eda3
0x34b655…2a6f
8 touches
6 conflicts
0x6a925e11…2653
0x34b655…2a6f
8 touches
6 conflicts
0x6d5fe8e7…2071
0x34b655…2a6f
8 touches
6 conflicts
0xb2560305…f27d
0x34b655…2a6f
8 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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 0xea79e6d350…ec68ad
Audit this contract →
← previous block·next block →recent activity