pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,596,736
← previous block
next block →
recent activity
Analyzing
Block #85,596,736
9 transactions · 8 stateful · 2026-07-04 18:16:38 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,596,736
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#6
0x6a494e7e
#7
setData
#5
execFwdPositionOps
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x05475161…1bd5
0x34b655…2a6f
2 touches
0 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
2 touches
0 conflicts
0x287d281e…bdc1
0x34b655…2a6f
2 touches
0 conflicts
0x38a6ef6a…4fee
0x34b655…2a6f
2 touches
0 conflicts
0x427d1120…4eb1
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
0x033cf007c8…d2136d
Audit this contract →
← previous block
·
next block →
recent activity