pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,489,899
← previous block
next block →
recent activity
Analyzing
Block #96,489,899
9 transactions · 8 stateful · 2026-08-16 12:28:48 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,489,899
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x61d59c2d
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0xb276d3e0…9cfd
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0808ec9f…45fb
0x34b655…2a6f
2 touches
0 conflicts
0x1565183a…e0a0
0x34b655…2a6f
2 touches
0 conflicts
0x4d5053d1…3b7d
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
0x5e71af988f…8cbfd6
Audit this contract →
← previous block
·
next block →
recent activity