pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,579,046
← previous block
next block →
recent activity
Analyzing
Block #89,579,046
14 transactions · 9 stateful · 2026-07-23 05:56:11 UTC
Parallelism
86
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,579,046
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
#3
execPerpOps
#4
execPerpOps
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#9
execOrders
#10
transfer
#11
transfer
#12
setData
#13
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c9704c…8a57
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x039c2f44…9ac7
0x34b655…2a6f
2 touches
0 conflicts
0x05975727…7fcf
0x34b655…2a6f
2 touches
0 conflicts
0x177f8108…ff11
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2266
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
0x95c9704c08…fd8a57
Audit this contract →
← previous block
·
next block →
recent activity