pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,187,529
← previous block
next block →
recent activity
Analyzing
Block #85,187,529
11 transactions · 9 stateful · 2026-07-02 20:51:24 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,187,529
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execPerpOps
#3
exactInputSingle
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
execute
#8
closeBetting
#9
setData
#10
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0xda8d6085…7b09
0x34b655…2a6f
4 touches
1 conflict
0xb7cb6e3c…f744
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x2a4bc61a…655a
0x34b655…2a6f
4 touches
1 conflict
0xf07bd4ca…f12d
0x34b655…2a6f
3 touches
1 conflict
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
0x5e782d178d…db5317
Audit this contract →
← previous block
·
next block →
recent activity