pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,467,304
← previous block
next block →
recent activity
Analyzing
Block #97,467,304
13 transactions · 13 stateful · 2026-08-19 23:10:26 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,467,304
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
updatePrices
#3
0xab083028
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
updatePosition
#8
0x3f5c179b
#9
execFwdPositionOpsV2
#10
setData
#11
0x59558d29
#12
execOrders
#4
0xe3a3c9cc
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62601310…c90b
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xb3fc9a5a…0820
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065d
0x188d58…ea8e
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
0x62601310fd…5fc90b
Audit this contract →
← previous block
·
next block →
recent activity