pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,496,753
← previous block
next block →
recent activity
Analyzing
Block #97,496,753
11 transactions · 10 stateful · 2026-08-20 01:38:49 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,496,753
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInput
#2
0x41a8f47c
· blocks 1
#4
execOrder
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#8
execFwdPositionOpsV2
#9
forward
#10
setData
#3
0x0c7abd22
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69236ced…f2d0
0x34b655…2a6f
4 touches
1 conflict
0x71a9c98c…7d73
0x34b655…2a6f
4 touches
1 conflict
0x78fb0f88…bea8
0x40c49f…2af0
3 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0005
0x103de0…bb55
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x06cdf7f0…fbe6
0x3bd359…433a
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
0x69236cedb8…22f2d0
Audit this contract →
← previous block
·
next block →
recent activity