← previous blocknext block →recent activity
Analyzing
Block #106,956,636
25 transactions · 22 stateful · 2026-09-22 05:52:49 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,956,636 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w310w011w212w113w317w218w019w122w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b7196f5…473a
0x34b655…2a6f
8 touches
6 conflicts
0xbc79e409…cece
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
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
6 conflicts on slot 0x6b7196f527…4d473a
Audit this contract →
← previous block·next block →recent activity