pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,726,546
← previous block
next block →
recent activity
Analyzing
Block #95,726,546
9 transactions · 8 stateful · 2026-08-13 20:28:52 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
#95,726,546
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOpsV2
· blocks 1
#4
setData
#6
updateDataFeedsValuesPartial
#7
0xd708c5d8
#8
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x0728ec77…146c
0x34b655…2a6f
2 touches
0 conflicts
0x1c1fbb6a…b7df
0x34b655…2a6f
2 touches
0 conflicts
0x27099c8c…d9d5
0x34b655…2a6f
2 touches
0 conflicts
0x30ae635d…5e67
0x34b655…2a6f
2 touches
0 conflicts
0x463e8557…882c
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
0x00ddbbf292…ff4588
Audit this contract →
← previous block
·
next block →
recent activity