← previous blocknext block →recent activity
Analyzing
Block #86,656,942
21 transactions · 18 stateful · 2026-07-09 16:15:25 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,656,942 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w19w110w211w319w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x9355efee…7bcd
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0xdbd174e4…b6f8
0x34b655…2a6f
6 touches
3 conflicts
0x7a693a45…747c
0x34b655…2a6f
6 touches
3 conflicts
0x899723a2…657b
0x34b655…2a6f
6 touches
3 conflicts
0x342f88f5…2a06
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity