pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,167,491
← previous block
next block →
recent activity
Analyzing
Block #85,167,491
13 transactions · 10 stateful · 2026-07-02 18:37:58 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,167,491
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#3
0xa96df62f
#4
0x0c7abd22
#5
0xccf50a51
#6
updateDataFeedsValuesPartial
#7
0x62be7533
#8
forward
#9
0x0f6795d9
#10
setData
#11
0x39435dac
#12
0xc7e3ec2c
#2
0xaf5e395a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x973e943b…0e23
0x065c9d…c394
2 touches
0 conflicts
0xb6dc4957…b608
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x16d564…365f
2 touches
0 conflicts
0x00000000…0001
0x16d564…365f
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity