pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,320,673
← previous block
next block →
recent activity
Analyzing
Block #98,320,673
16 transactions · 12 stateful · 2026-08-22 23:12:22 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,320,673
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x0c7abd22
#2
0x7b84f330
#3
execOrders
#4
0x6ad2e98b
#5
execOrder
#6
0x59558d29
#7
modifyLiquidities
#8
0x5acec890
#9
execFwdPositionOpsV2
#10
executeBatch
#11
execFwdPositionOpsV2
#12
forward
#13
setData
#14
0x4f3b2b…a7b4
#15
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
0xac601417…393d
0x188d58…ea8e
2 touches
0 conflicts
0xd62d16a4…4b0e
0x188d58…ea8e
2 touches
0 conflicts
0xe1611ccd…0597
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0x29ab4ba1…2696
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