← previous blocknext block →recent activity
Analyzing
Block #86,666,403
20 transactions · 17 stateful · 2026-07-09 17:18:32 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,666,403 · 20 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
4w05w16w27w38w210w011w012w113w115w416w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x3ddbf624…b01c
0x34b655…2a6f
6 touches
3 conflicts
0x47141f0a…2af2
0x34b655…2a6f
6 touches
3 conflicts
0x51f0a25b…e81f
0x34b655…2a6f
6 touches
3 conflicts
0x5938afe1…fc61
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
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 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity