← previous blocknext block →recent activity
Analyzing
Block #86,663,815
26 transactions · 22 stateful · 2026-07-09 17:01:17 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,663,815 · 26 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
2w07w08w19w210w313w014w115w416w517w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x87f3dc22…eb64
0x34b655…2a6f
8 touches
6 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
8 touches
6 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
8 touches
6 conflicts
0xe727ab72…768b
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity