← previous blocknext block →recent activity
Analyzing
Block #86,660,649
24 transactions · 17 stateful · 2026-07-09 16:40:11 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,660,649 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w313w214w021w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
8 touches
6 conflicts
0x660c9d95…7859
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0x8bc08bb8…de10
0x34b655…2a6f
6 touches
3 conflicts
0xa020506f…7c60
0x34b655…2a6f
6 touches
3 conflicts
0xa29182a1…c12c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity