pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,614,512
← previous block
next block →
recent activity
Analyzing
Block #85,614,512
9 transactions · 9 stateful · 2026-07-04 20:14:56 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,614,512
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 2
#2
removeLiquidity
#4
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#3
0xab083028
#5
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x8a17bfab…bf05
0x065c9d…c394
4 touches
1 conflict
0x80d7e539…3ffd
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x0fe66dd5…ed65
0x5afd3e…7620
2 touches
0 conflicts
0xcfa9f797…bf41
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity