pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,097,589
← previous block
next block →
recent activity
Analyzing
Block #91,097,589
10 transactions · 7 stateful · 2026-07-28 15:48:54 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,097,589
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
swapTokensSingleV3ERC20ToNative
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
execOrders
#8
approve
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70a2eb8e…ba35
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xf0b9b3ee…c064
0x000000…012a
2 touches
0 conflicts
0x7b2acdae…1ba2
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x155e52ca…fac7
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:
Perpl
1 conflict on slot
0x70a2eb8e28…92ba35
Audit this contract →
← previous block
·
next block →
recent activity