pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,529,740
← previous block
next block →
recent activity
Analyzing
Block #85,529,740
12 transactions · 11 stateful · 2026-07-04 10:50:25 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,529,740
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
· blocks 1
#2
removeLiquidity
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updatePrices
#8
exactInputSingle
#9
0x0f6795d9
#10
setData
#11
0xc7e3ec2c
#7
0x50a0b275
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa307c334…c9ae
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0xcb643582…2626
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x1b3d67ac…79f3
0x5afd3e…7620
2 touches
0 conflicts
0x53c943ff…8ce1
0x5afd3e…7620
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
0xa307c33491…77c9ae
Audit this contract →
← previous block
·
next block →
recent activity