← previous blocknext block →recent activity
Analyzing
Block #86,454,718
20 transactions · 19 stateful · 2026-07-08 17:40:58 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,454,718 · 20 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
1w02w13w24w35w26w38w09w110w211w313w014w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xdf042143…3459
0xd32edf…ff58
7 touches
6 conflicts
0x3133f94b…f76b
0x34b655…2a6f
6 touches
3 conflicts
0x66187b06…b386
0x34b655…2a6f
6 touches
3 conflicts
0x69613cc6…2d0d
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x752b03c4…232a
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