pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,220,203
← previous block
next block →
recent activity
Analyzing
Block #85,220,203
10 transactions · 7 stateful · 2026-07-03 00:28:59 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,220,203
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
verifyOracleProofV2
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#8
0x895d10d3
#9
0xc7e3ec2c
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2bb41ab1…e5e7
0x34b655…2a6f
2 touches
0 conflicts
0x4a0db291…8568
0x34b655…2a6f
2 touches
0 conflicts
0x4b18285e…24b3
0x34b655…2a6f
2 touches
0 conflicts
0x551839d9…736d
0x34b655…2a6f
2 touches
0 conflicts
0x57a080db…7fde
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
0x0950060282…6794ea
Audit this contract →
← previous block
·
next block →
recent activity