pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,692,635
← previous block
next block →
recent activity
Analyzing
Block #97,692,635
12 transactions · 11 stateful · 2026-08-20 18:15:26 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,692,635
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
execPerpOps
#3
0x5acec890
· blocks 1
#5
execFwdPositionOpsV2
#6
batchUpdate
#7
depositTo
#8
setData
· blocks 1
#10
0x7a0ffa…a0be
#11
0x59558d29
#4
execFwdPositionOpsV2
#9
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157b6348…8604
0x34b655…2a6f
4 touches
1 conflict
0xe429e4c9…9510
0x34b655…2a6f
4 touches
1 conflict
0xfd0c2151…72ae
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0005
0x103de0…bb55
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x4f59b1b4…3d3e
0x40c49f…2af0
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
0x157b634872…098604
Audit this contract →
← previous block
·
next block →
recent activity