pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,592,461
← previous block
next block →
recent activity
Analyzing
Block #85,592,461
10 transactions · 8 stateful · 2026-07-04 17:48:09 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,592,461
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
· blocks 2
#6
execFwdPositionOps
#7
0x6a4947d1
#8
setData
#5
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x41cd7efa…7d03
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd40df912…a46c
0x34b655…2a6f
4 touches
1 conflict
0x72ec3615…68d4
0x34b655…2a6f
3 touches
1 conflict
0x34518ce2…7a66
0x34b655…2a6f
2 touches
0 conflicts
0x42e40b2d…5d87
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
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
3 conflicts on slot
0xc0eb79d1cb…5529a4
Audit this contract →
← previous block
·
next block →
recent activity