pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,915,152
← previous block
next block →
recent activity
Analyzing
Block #95,915,152
10 transactions · 9 stateful · 2026-08-14 12:17:44 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,915,152
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOpsV2
· blocks 2
#5
updateDataFeedsValuesPartial
#6
execOrders
#7
setData
#8
execute
#9
0x61d59c2d
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x0b1a9431…183e
0x34b655…2a6f
2 touches
0 conflicts
0x0f6aef87…8137
0x34b655…2a6f
2 touches
0 conflicts
0x33018b40…8465
0x34b655…2a6f
2 touches
0 conflicts
0x3f798539…99c4
0x34b655…2a6f
2 touches
0 conflicts
0x43076802…d920
0x34b655…2a6f
2 touches
0 conflicts
0x4dc18bef…59d5
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
0xa3a621f8f3…6975a2
Audit this contract →
← previous block
·
next block →
recent activity