pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,512,779
← previous block
next block →
recent activity
Analyzing
Block #96,512,779
10 transactions · 8 stateful · 2026-08-16 14:24:11 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,512,779
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
artefact_keep
#4
execFwdPositionOpsV2
· blocks 2
#7
setData
#8
0x61d59c2d
#9
execOrders
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x9b691eb5…6a21
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721c
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x3ac0ead0…e0e3
0x34b655…2a6f
4 touches
1 conflict
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
0x91b0f8edc5…b76bd7
Audit this contract →
← previous block
·
next block →
recent activity