pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,384,947
← previous block
next block →
recent activity
Analyzing
Block #97,384,947
11 transactions · 9 stateful · 2026-08-19 15:57:40 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,384,947
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#3
exactInputSingle
#5
0x3f5c179b
#6
execFwdPositionOpsV2
#7
setData
#8
0x4cb2db39
#9
0x59558d29
#10
execOrders
#2
execOrder
· blocks 1
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967ba723…6d0f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x166b4bb9…a1e7
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x3aee421b…c4ba
0x34b655…2a6f
2 touches
0 conflicts
0x3bea5e22…143f
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
3 conflicts on slot
0x967ba7239d…2d6d0f
Audit this contract →
← previous block
·
next block →
recent activity