pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,612,840
← previous block
next block →
recent activity
Analyzing
Block #97,612,840
10 transactions · 10 stateful · 2026-08-20 11:25:50 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,612,840
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
execOrders
· blocks 1
#3
execOrder
· blocks 1
#5
0x5acec890
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
0x59558d29
#4
execOrder
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
4 touches
1 conflict
0x88724b87…5e65
0x34b655…2a6f
4 touches
1 conflict
0x2e5cdd04…22ab
0x34b655…2a6f
4 touches
1 conflict
0x4ad7a3f0…a9e2
0x000000…012a
2 touches
0 conflicts
0x9cafc3b6…ee8c
0x000000…012a
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0005
0x103de0…bb55
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
0x40ac662f45…43df77
Audit this contract →
← previous block
·
next block →
recent activity