pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,604,060
← previous block
next block →
recent activity
Analyzing
Block #97,604,060
13 transactions · 8 stateful · 2026-08-20 10:41:05 UTC
Parallelism
69
/100
Blocked
38
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,604,060
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
exactInputSingle
#3
forward
#4
execFwdPositionOpsV2
#5
setData
#6
0x59558d29
#7
0xb8024e73
#8
execOrders
#9
execOrders
· blocks 3
#10
execOrders
· blocks 2
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
11
w2
12
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x06754f35…108d
0x34b655…2a6f
2 touches
0 conflicts
0x17c93766…889e
0x34b655…2a6f
2 touches
0 conflicts
0x32cd523f…9885
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x53baa009…68b3
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
6 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity