pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,838,512
← previous block
next block →
recent activity
Analyzing
Block #98,838,512
9 transactions · 9 stateful · 2026-08-24 19:14:11 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,838,512
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
0x3f5c179b
#4
execFwdPositionOpsV2
#5
withdraw
· blocks 2
#8
setData
#6
withdraw
· blocks 1
#7
withdraw
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51dc
0x69a5f9…2fef
6 touches
3 conflicts
0x2ef1d89b…196d
0x754704…b603
6 touches
3 conflicts
0xfda39b6f…d4cc
0x754704…b603
6 touches
3 conflicts
0x00000000…0036
0x35a73b…6042
6 touches
3 conflicts
0xaf831072…51d5
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51d6
0x69a5f9…2fef
6 touches
3 conflicts
0x2ad2f4bc…1800
0x34b655…2a6f
2 touches
0 conflicts
0x31147dde…390f
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:
0x69a5f9ad…102fef
3 conflicts on slot
0xaf831072f6…c551dc
Audit this contract →
← previous block
·
next block →
recent activity