pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,289,634
← previous block
next block →
recent activity
Analyzing
Block #96,289,634
8 transactions · 8 stateful · 2026-08-15 19:41:34 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,289,634
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#2
0xb5ce855a
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf653ebdf…16c7
0x754704…b603
4 touches
1 conflict
0x6b6cb5ca…cebf
0x0a4fcb…a602
4 touches
1 conflict
0x6b6cb5ca…cec0
0x0a4fcb…a602
4 touches
1 conflict
0x6b6cb5ca…cec1
0x0a4fcb…a602
4 touches
1 conflict
0x6bd9b2de…7d72
0x0f2610…0edc
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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:
USDC (USDC)
1 conflict on slot
0xf653ebdf57…8816c7
Audit this contract →
← previous block
·
next block →
recent activity