pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,989,213
← previous block
next block →
recent activity
Analyzing
Block #97,989,213
14 transactions · 14 stateful · 2026-08-21 19:23:25 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,989,213
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
updatePrices
#3
execOrders
#4
0xb2d4797b
#5
executeBatch
#6
setData
#7
execFwdPositionOpsV2
#8
updatePosition
#9
execFwdPositionOpsV2
#10
0xed82b078
#11
commit
#12
swapExactTokensForTokens
#13
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x076b9edf…e35c
0x34b655…2a6f
2 touches
0 conflicts
0x3acf9416…7ddc
0x34b655…2a6f
2 touches
0 conflicts
0x5934b407…e058
0x34b655…2a6f
2 touches
0 conflicts
0x64499a61…d650
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
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:
0x34014398…d1768f
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity