← previous blocknext block →recent activity
Analyzing
Block #86,700,372
15 transactions · 14 stateful · 2026-07-09 21:05:14 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,700,372 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w010w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfaef7662…f79b
0x34b655…2a6f
4 touches
1 conflict
0x07b979bc…3564
0xb1dbf0…c0d3
4 touches
1 conflict
0x2a4568fd…f2de
0x34b655…2a6f
4 touches
1 conflict
0x2f0505af…422a
0x34b655…2a6f
4 touches
1 conflict
0x344fb75a…3d39
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity