pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,134,206
← previous block
next block →
recent activity
Analyzing
Block #86,134,206
12 transactions · 10 stateful · 2026-07-07 06:00:25 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,134,206
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
execOrders
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execPerpOps
#6
execPerpOps
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a4c9671
#10
setData
#11
execOrders
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x225c3858…2a9b
0x34b655…2a6f
2 touches
0 conflicts
0x2f7781d6…e632
0x34b655…2a6f
2 touches
0 conflicts
0x30fa662a…06e0
0x34b655…2a6f
2 touches
0 conflicts
0x33ba8d56…f421
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x86cea35b12…8ebdff
Audit this contract →
← previous block
·
next block →
recent activity