← previous blocknext block →recent activity
Analyzing
Block #86,700,307
14 transactions · 11 stateful · 2026-07-09 21:04:48 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,700,307 · 14 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
6w07w18w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x949fc5d9…55f3
0x34b655…2a6f
4 touches
1 conflict
0xa4c4b591…7f9f
0x34b655…2a6f
4 touches
1 conflict
0xa5f65358…b877
0x34b655…2a6f
4 touches
1 conflict
0xc2ebcc0c…2261
0x34b655…2a6f
4 touches
1 conflict
0xca57a4ab…b781
0x34b655…2a6f
4 touches
1 conflict
0xe613a978…22a4
0x34b655…2a6f
4 touches
1 conflict
0x1bde87f2…0843
0x34b655…2a6f
4 touches
1 conflict
0x36077f58…66cd
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 0x949fc5d98c…1955f3
Audit this contract →
← previous block·next block →recent activity