← previous blocknext block →recent activity
Analyzing
Block #86,790,560
47 transactions · 36 stateful · 2026-07-10 07:07:36 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.49
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,790,560 · 47 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w110w111w212w013w420w021w122w223w324w425w526w627w736w537w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x0c2ce4cd…005f
0x34b655…2a6f
10 touches
10 conflicts
0x79d50d4a…951d
0x34b655…2a6f
10 touches
10 conflicts
0x7f8ac7a3…4820
0xd32edf…ff58
9 touches
10 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity