← previous blocknext block →recent activity
Analyzing
Block #86,848,139
10 transactions · 7 stateful · 2026-07-10 13:32:34 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,848,139 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32646adf…e05d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
2 touches
0 conflicts
0x1acd3c25…9d08
0x34b655…2a6f
2 touches
0 conflicts
0x2efd1517…0726
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x32646adf44…b6e05d
Audit this contract →
← previous block·next block →recent activity