← previous blocknext block →recent activity
Analyzing
Block #86,617,046
21 transactions · 20 stateful · 2026-07-09 11:47:35 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,617,046 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w010w411w115w516w118w019w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b87e4d…65d5
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x0f2a6e9f…ff3b
0x34b655…2a6f
8 touches
6 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
8 touches
6 conflicts
0x400fb569…d594
0x34b655…2a6f
6 touches
3 conflicts
0x4a8cbb6a…61cd
0x34b655…2a6f
6 touches
3 conflicts
0x5484ad2c…7bb3
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x70b87e4d96…6c65d5
Audit this contract →
← previous block·next block →recent activity