pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,671,514
← previous block
next block →
recent activity
Analyzing
Block #97,671,514
12 transactions · 12 stateful · 2026-08-20 16:27:38 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,671,514
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
setPrice
#3
setPrice
#4
setPrice
#5
setPrice
#6
setPriceForArbitrum
#7
updatePosition
#8
execFwdPositionOpsV2
· blocks 1
#10
setData
#11
0x59558d29
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a957fbd…6839
0x34b655…2a6f
4 touches
1 conflict
0x3df3de0d…cd8b
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0068
0x3c2269…cf62
2 touches
0 conflicts
0x0e268146…c1e1
0x3c2269…cf62
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
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
0x3a957fbd49…5f6839
Audit this contract →
← previous block
·
next block →
recent activity