pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,717,587
← previous block
next block →
recent activity
Analyzing
Block #95,717,587
11 transactions · 11 stateful · 2026-08-13 19:43:49 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,717,587
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execPerpOps
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
batchUpdate
#6
0x94defb17
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execOrders
#8
execFwdPositionOpsV2
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
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7bf6a41f…a17d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
2 touches
0 conflicts
0x972e38eb…dc76
0x34b655…2a6f
2 touches
0 conflicts
0x98a1bad6…5130
0x34b655…2a6f
2 touches
0 conflicts
0x9e599b87…c270
0x34b655…2a6f
2 touches
0 conflicts
0xa9af0099…3165
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity