← previous blocknext block →recent activity
Analyzing
Block #106,567,647
25 transactions · 22 stateful · 2026-09-20 21:13:58 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,567,647 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w010w111w212w013w116w320w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eca6bab…e518
0x34b655…2a6f
10 touches
10 conflicts
0x3a429191…9cda
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x2e7d7640…5831
0x34b655…2a6f
6 touches
3 conflicts
0x1adde00d…ed31
0xa6afd3…d132
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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
10 conflicts on slot 0x9eca6babcc…dbe518
Audit this contract →
← previous block·next block →recent activity