← previous blocknext block →recent activity
Analyzing
Block #86,966,031
22 transactions · 17 stateful · 2026-07-11 02:40:39 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,966,031 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w010w011w112w213w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0e9b4342…0a32
0xd32edf…ff58
7 touches
6 conflicts
0x0b277fb8…2d81
0x34b655…2a6f
6 touches
3 conflicts
0x0b277fb8…2d82
0x34b655…2a6f
6 touches
3 conflicts
0x20492d53…80f9
0x34b655…2a6f
6 touches
3 conflicts
0x56dd139b…40d3
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity