← previous blocknext block →recent activity
Analyzing
Block #86,961,657
28 transactions · 24 stateful · 2026-07-11 02:11:25 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,961,657 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w411w512w613w714w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xdef9f986…2ed0
0xd32edf…ff58
13 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xae901867…8085
0x34b655…2a6f
8 touches
6 conflicts
0xae901867…8086
0x34b655…2a6f
8 touches
6 conflicts
0xf982b915…898b
0x34b655…2a6f
8 touches
6 conflicts
0x809f2ba8…89d3
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity