pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,174,015
← previous block
next block →
recent activity
Analyzing
Block #85,174,015
10 transactions · 9 stateful · 2026-07-02 19:21:21 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,174,015
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execPerpOps
· blocks 1
#4
0xe2dc7dc3
#5
execFwdPositionOps
#6
batchUpdate
#7
closeTrade
#8
0x6a46baa9
#9
setData
#3
execPerpOps
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
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x319d9fba…6ff3
0x1efe02…37d6
2 touches
0 conflicts
0xa916a5af…1459
0x1efe02…37d6
2 touches
0 conflicts
0xfa1b3dd2…4d32
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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
0xac2a02739b…817212
Audit this contract →
← previous block
·
next block →
recent activity