pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,898,175
← previous block
next block →
recent activity
Analyzing
Block #97,898,175
13 transactions · 12 stateful · 2026-08-21 11:40:19 UTC
Parallelism
85
/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,898,175
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execOrders
#3
execPerpOps
#4
execPerpOps
#5
0x928e4afa
· blocks 1
#7
approve
#8
execFwdPositionOpsV2
#9
0xed82b078
#10
0xed82b078
#11
setData
#12
0x59558d29
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x404e820d…17b5
0x34b655…2a6f
4 touches
1 conflict
0x44d383ab…5c7c
0x34b655…2a6f
4 touches
1 conflict
0x5ca8e4c7…77de
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x79a35e18…5e01
0x34b655…2a6f
4 touches
1 conflict
0xc6ff19c6…5250
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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: Settlement / Helper
1 conflict on slot
0xad3e66bedd…10dccc
Audit this contract →
← previous block
·
next block →
recent activity