pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,278,710
← previous block
next block →
recent activity
Analyzing
Block #91,278,710
13 transactions · 11 stateful · 2026-07-29 07:00:54 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
#91,278,710
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
0x6a69a59d
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
exactInputSingle
#7
execFwdPositionOps
· blocks 1
#9
0x94defb17
#10
0xed82b078
#11
setData
#12
0x59558d29
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x156ea0a2…0b55
0x34b655…2a6f
2 touches
0 conflicts
0x2a31ba55…4765
0x34b655…2a6f
2 touches
0 conflicts
0x3be4b35d…137f
0x34b655…2a6f
2 touches
0 conflicts
0x4102cb2a…3b17
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a2
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity