← previous blocknext block →recent activity
Analyzing
Block #86,914,828
15 transactions · 14 stateful · 2026-07-10 20:58:31 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,914,828 · 15 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
2w03w14w25w36w48w19w010w211w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x1f44bdf9…51aa
0x34b655…2a6f
8 touches
6 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x342cf4de…0a48
0x34b655…2a6f
8 touches
6 conflicts
0x4ac63542…19bb
0x34b655…2a6f
8 touches
6 conflicts
0x4cff6c4d…f90c
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity