pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,707,450
← previous block
next block →
recent activity
Analyzing
Block #85,707,450
12 transactions · 11 stateful · 2026-07-05 06:35:09 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,707,450
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execPerpOps
#5
execPerpOps
#6
execFwdPositionOps
· blocks 1
#8
setData
#9
0x6a49fb95
#10
execOrders
#11
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x557d3a49…cc33
0x34b655…2a6f
2 touches
0 conflicts
0x77d4ad2d…583c
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x0950060282…6794ea
Audit this contract →
← previous block
·
next block →
recent activity