pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,537,234
← previous block
next block →
recent activity
Analyzing
Block #98,537,234
13 transactions · 13 stateful · 2026-08-23 17:29:19 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,537,234
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0xab083028
· blocks 2
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#7
delegate
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#12
setData
#10
0xed82b078
#11
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7339ac40…28ef
0x065c9d…c394
3 touches
1 conflict
0x2e49d3eb…fa7c
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x02373c43…3cb3
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x4175529119…79977f
Audit this contract →
← previous block
·
next block →
recent activity