pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,116,286
← previous block
next block →
recent activity
Analyzing
Block #96,116,286
11 transactions · 7 stateful · 2026-08-15 05:09:38 UTC
Parallelism
73
/100
Blocked
43
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,116,286
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#9
execOrders
#10
setData
#2
execOrder
· blocks 2
#3
execOrder
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1b1d960e…13de
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
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
3 conflicts on slot
0xd66696e0dc…230842
Audit this contract →
← previous block
·
next block →
recent activity