pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,564,310
← previous block
next block →
recent activity
Analyzing
Block #98,564,310
14 transactions · 14 stateful · 2026-08-23 19:50:43 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,564,310
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
0x8263f5d9
#4
execOrders
#5
exactInputSingle
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0x3f5c179b
#11
0x57368ddf
#12
0x94defb17
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x17e02d34…dac8
0x34b655…2a6f
2 touches
0 conflicts
0x1c56c3ad…0c7f
0x34b655…2a6f
2 touches
0 conflicts
0x2c9d2f48…8fc2
0x34b655…2a6f
2 touches
0 conflicts
0x37b1078b…e857
0x34b655…2a6f
2 touches
0 conflicts
0x4b3b06fc…f6e2
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.
← previous block
·
next block →
recent activity