pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,535,446
← previous block
next block →
recent activity
Analyzing
Block #96,535,446
8 transactions · 7 stateful · 2026-08-16 16:18:11 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,535,446
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d63a6…731e
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
artefact_keep
#5
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xa307d5f3…38a9
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
2 touches
0 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
2 touches
0 conflicts
0x46c8e565…d7a8
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
0x957c875f2a…99b3f9
Audit this contract →
← previous block
·
next block →
recent activity