pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,557,165
← previous block
next block →
recent activity
Analyzing
Block #96,557,165
10 transactions · 8 stateful · 2026-08-16 18:07:24 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,557,165
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x5acec890
#4
updatePrices
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#3
0x5acec890
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe2addb64…3da9
0x34b655…2a6f
4 touches
1 conflict
0x7fa3f3d4…195b
0x34b655…2a6f
4 touches
1 conflict
0x0bcb2b72…5d1d
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2ffa0115…ed47
0x34b655…2a6f
2 touches
0 conflicts
0x3a9e59a0…6198
0x34b655…2a6f
2 touches
0 conflicts
0x5f447bf3…57c7
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity