pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,167,027
← previous block
next block →
recent activity
Analyzing
Block #85,167,027
11 transactions · 11 stateful · 2026-07-02 18:34:52 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,167,027
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 1
#4
closeTrade
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a46afc4
#8
setData
#9
execOrders
#10
0xc7e3ec2c
#3
execFwdPositionOps
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
0x68f60ae6…7d65
0x34b655…2a6f
4 touches
1 conflict
0x0e5f2a94…4732
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1757b8ff…9a71
0x34b655…2a6f
2 touches
0 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
2 touches
0 conflicts
0x594b8031…7e93
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
1 conflict on slot
0x68f60ae6d8…027d65
Audit this contract →
← previous block
·
next block →
recent activity