pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,333,408
← previous block
next block →
recent activity
Analyzing
Block #98,333,408
22 transactions · 19 stateful · 2026-08-23 00:16:26 UTC
Parallelism
91
/100
Blocked
11
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,333,408
· 22 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
0x7b84f330
#4
0x6a8a3c51
· blocks 1
#5
exactInputSingle
#6
updatePrices
#7
execOrders
#8
execOrders
#9
updateDataFeedsValuesPartial
#10
0x59558d29
#11
execPerpOps
#12
execPerpOps
#14
execFwdPositionOpsV2
· blocks 1
#15
execFwdPositionOpsV2
· blocks 1
#16
0xed82b078
#17
0xed82b078
#18
setData
#19
fulfillOrder
#20
execOrders
#13
0x6a8a3c51
#21
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
13
w1
14
w0
15
w0
21
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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
0x3090882336…22a62d
Audit this contract →
← previous block
·
next block →
recent activity