← previous blocknext block →recent activity
Analyzing
Block #86,671,992
21 transactions · 18 stateful · 2026-07-09 17:55:52 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,671,992 · 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
1w03w04w15w26w38w19w010w111w212w318w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2a6e9f…ff3b
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x2378c722…bff5
0x34b655…2a6f
8 touches
6 conflicts
0x400fb569…d594
0x34b655…2a6f
8 touches
6 conflicts
0xeaa801fb…dda1
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 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 0x0f2a6e9fd2…daff3b
Audit this contract →
← previous block·next block →recent activity