pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,662,725
← previous block
next block →
recent activity
Analyzing
Block #98,662,725
13 transactions · 11 stateful · 2026-08-24 04:23:29 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,662,725
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
matchOrders
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
execFwdPositionOpsV2
· blocks 1
#10
transfer
#11
setData
· blocks 1
#9
execFwdPositionOpsV2
#12
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x14cc77c7…69c4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5d601639…d720
0x340143…768f
2 touches
0 conflicts
0x065ff70b…356d
0x40c49f…2af0
2 touches
0 conflicts
0x9693a132…a518
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
0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block
·
next block →
recent activity