← previous blocknext block →recent activity
Analyzing
Block #86,220,869
17 transactions · 16 stateful · 2026-07-07 15:39:02 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,220,869 · 17 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
3w04w15w28w313w014w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x826cce18…251c
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x7babfe9a…ff96
0x34b655…2a6f
4 touches
1 conflict
0x8cf924ac…c2d8
0x34b655…2a6f
4 touches
1 conflict
0x917a162a…7665
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
3 conflicts on slot 0x53b4ef2b77…528a05
Audit this contract →
← previous block·next block →recent activity