pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,797,346
← previous block
next block →
recent activity
Analyzing
Block #96,797,346
12 transactions · 10 stateful · 2026-08-17 14:15:26 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,797,346
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 2
#2
execOrder
#4
updatePrices
#5
execOrders
· blocks 1
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#11
execOrders
#3
execOrder
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x315e07b8…9823
0x34b655…2a6f
2 touches
0 conflicts
0x49887f7e…9e7c
0x34b655…2a6f
2 touches
0 conflicts
0x4d236921…feff
0x34b655…2a6f
2 touches
0 conflicts
0x660dab48…6990
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
0x0672e4a279…2f8d1f
Audit this contract →
← previous block
·
next block →
recent activity