pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,569,055
← previous block
next block →
recent activity
Analyzing
Block #96,569,055
9 transactions · 7 stateful · 2026-08-16 19:07:13 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,569,055
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xc9623387
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
execOrders
#8
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7af4f66c…3565
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x40856fd2…0eb9
0x34b655…2a6f
2 touches
0 conflicts
0x4918ae06…9b39
0x34b655…2a6f
2 touches
0 conflicts
0x65ceec63…29d9
0x34b655…2a6f
2 touches
0 conflicts
0x7d0eaae2…60b7
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
0x7af4f66c75…4b3565
Audit this contract →
← previous block
·
next block →
recent activity