pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,482,756
← previous block
next block →
recent activity
Analyzing
Block #96,482,756
7 transactions · 4 stateful · 2026-08-16 11:52:52 UTC
Parallelism
57
/100
Blocked
50
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,482,756
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
setData
#2
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbda32af…5a25
0x34b655…2a6f
6 touches
3 conflicts
0xad90f74b…4a9e
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x2fceaa3d…d516
0x34b655…2a6f
2 touches
0 conflicts
0x588380ee…0a5c
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
3 conflicts on slot
0xcbda32af61…265a25
Audit this contract →
← previous block
·
next block →
recent activity