pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,575,391
← previous block
next block →
recent activity
Analyzing
Block #98,575,391
14 transactions · 11 stateful · 2026-08-23 20:48:38 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,575,391
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
matchOrders
#2
0xa96df62f
#3
0x8263f5d9
#4
exactInputSingle
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x6a8b5d1d
#10
0x29c982…d178
#11
0x41549a…56ca
#12
0x4473ad…47bd
#13
setData
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
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x1686502b…a1d2
0x3bd359…433a
2 touches
0 conflicts
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
0x0eff0903…8165
0x754704…b603
2 touches
0 conflicts
0x777c9106…162a
0x754704…b603
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