pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,333,487
← previous block
next block →
recent activity
Analyzing
Block #98,333,487
14 transactions · 12 stateful · 2026-08-23 00:16:50 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,333,487
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x7b84f330
#3
0x7b84f330
#4
updatePrices
#5
0xab083028
#6
0x59558d29
#7
execPerpOps
#8
execPerpOps
#9
0x928e4afa
#10
execFwdPositionOpsV2
· blocks 1
#12
forward
#13
setData
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xad97622f…562a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0x2bcab7da…6268
0x34b655…2a6f
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
0x5e3014f0c7…b1b4e1
Audit this contract →
← previous block
·
next block →
recent activity