pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,838,768
← previous block
next block →
recent activity
Analyzing
Block #96,838,768
11 transactions · 11 stateful · 2026-08-17 17:43:47 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
#96,838,768
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
0x3f5c179b
#7
batchUpdate
#8
forward
#9
transfer
#10
setData
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x28f324ed…9db7
0x34b655…2a6f
2 touches
0 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
2 touches
0 conflicts
0x48203298…65cb
0x34b655…2a6f
2 touches
0 conflicts
0x63e9821b…584e
0x34b655…2a6f
2 touches
0 conflicts
0x79963e73…50be
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
0x734ee32053…cecaae
Audit this contract →
← previous block
·
next block →
recent activity