← previous blocknext block →recent activity
Analyzing
Block #86,609,694
22 transactions · 14 stateful · 2026-07-09 10:58:32 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,609,694 · 22 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
1w05w06w17w210w311w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xedcf2991…8551
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x67eb9f2d…885a
0x34b655…2a6f
6 touches
3 conflicts
0x350cdd8c…7cfb
0x34b655…2a6f
4 touches
1 conflict
0x4cce3b42…33ba
0x34b655…2a6f
4 touches
1 conflict
0x5b7d1494…ed87
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity