pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,769,060
← previous block
next block →
recent activity
Analyzing
Block #85,769,060
11 transactions · 8 stateful · 2026-07-05 13:25:12 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,769,060
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execPerpOps
#3
execFwdPositionOps
· blocks 1
#4
0x6df9e92b
#5
updateDataFeedsValuesPartial
#6
0x6a4a5bb0
#7
setData
#8
0xacdd7c…9c25
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5b60abd2…60e6
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x86a2da8d…a760
0x34b655…2a6f
4 touches
1 conflict
0x90d81b88…3a34
0x34b655…2a6f
4 touches
1 conflict
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 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
0x213a54fa2e…2fc85f
Audit this contract →
← previous block
·
next block →
recent activity