pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,676,647
← previous block
next block →
recent activity
Analyzing
Block #98,676,647
12 transactions · 10 stateful · 2026-08-24 05:35:51 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,676,647
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
depositNative
#2
setData
#3
0x32d01e04
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#8
0x3f5c179b
· blocks 1
#9
0x3f5c179b
#11
execFwdPositionOpsV2
#10
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x92f41d1f…4258
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x35e9988f…d2ec
0xa6afd3…d132
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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-WETH/USDC
1 conflict on slot
0x65021fefe6…cfb735
Audit this contract →
← previous block
·
next block →
recent activity