pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,576,601
← previous block
next block →
recent activity
Analyzing
Block #98,576,601
14 transactions · 13 stateful · 2026-08-23 20:54:57 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,576,601
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
exactInputSingle
#4
0x59558d29
#5
0x5acec890
· blocks 1
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
bet
#10
0x6a8b5e99
#11
setData
#12
execOrders
#13
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1686502b…a1d2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…0000
0x86dfd5…6a7d
2 touches
0 conflicts
0x00000000…0001
0x86dfd5…6a7d
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
0x89ac61bf64…6b9443
Audit this contract →
← previous block
·
next block →
recent activity