← previous blocknext block →recent activity
Analyzing
Block #86,911,989
14 transactions · 13 stateful · 2026-07-10 20:39:36 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,911,989 · 14 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
3w04w06w17w28w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24de48ed…b934
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x59ededb5…45c4
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xf2e22c06…42d6
0x34b655…2a6f
6 touches
3 conflicts
0x75959b84…9bda
0x34b655…2a6f
4 touches
1 conflict
0x03b16972…8f62
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 0x24de48eda6…74b934
Audit this contract →
← previous block·next block →recent activity