pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,545,401
← previous block
next block →
recent activity
Analyzing
Block #96,545,401
10 transactions · 8 stateful · 2026-08-16 17:08:15 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,545,401
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#2
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x57368ddf
#7
execFwdPositionOpsV2
#8
transfer
#9
execOrders
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0xc62e31bf…b30a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x10f18761…8e0c
0x34b655…2a6f
2 touches
0 conflicts
0x27fa4ef5…9cba
0x34b655…2a6f
2 touches
0 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x30d58b0b…8806
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
0xabf57eb66c…0a416d
Audit this contract →
← previous block
·
next block →
recent activity