pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,608,798
← previous block
next block →
recent activity
Analyzing
Block #96,608,798
9 transactions · 8 stateful · 2026-08-16 22:27:07 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,608,798
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
execFwdPositionOpsV2
#5
0x57368ddf
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
setData
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x07969058…0fef
0x34b655…2a6f
2 touches
0 conflicts
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
2 touches
0 conflicts
0x2c1ede24…393f
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
0x02991b41c5…1a19e6
Audit this contract →
← previous block
·
next block →
recent activity