pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,691,839
← previous block
next block →
recent activity
Analyzing
Block #97,691,839
13 transactions · 11 stateful · 2026-08-20 18:11:24 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,691,839
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
0xa9b28aa6
#3
exactOutputSingle
#5
0x6ad2e98b
#6
0xe3a3c9cc
#7
0x5acec890
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0xed82b078
#11
setData
#12
0x59558d29
#4
execute
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
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x6146a721…e90d
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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:
USDC (USDC)
1 conflict on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity