pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,027,196
← previous block
next block →
recent activity
Analyzing
Block #96,027,196
8 transactions · 6 stateful · 2026-08-14 21:41:31 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,027,196
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOpsV2
· blocks 2
#3
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43076802…d920
0x34b655…2a6f
4 touches
1 conflict
0x09bde27f…671c
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x62738158…e746
0x34b655…2a6f
4 touches
1 conflict
0xfd4a5ef1…e4c4
0x34b655…2a6f
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
2 touches
0 conflicts
0x0f6aef87…8137
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
0x43076802ec…05d920
Audit this contract →
← previous block
·
next block →
recent activity