← previous blocknext block →recent activity
Analyzing
Block #86,787,687
20 transactions · 11 stateful · 2026-07-10 06:48:27 UTC
Parallelism
90/100
Blocked
36%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,787,687 · 20 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
1w02w04w18w09w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a310d83…cae0
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a59
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a5a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x846048e8…98f6
0x34b655…2a6f
4 touches
1 conflict
0xb95e925b…392d
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0x5a310d8339…49cae0
Audit this contract →
← previous block·next block →recent activity