pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,745,899
← previous block
next block →
recent activity
Analyzing
Block #85,745,899
13 transactions · 7 stateful · 2026-07-05 10:51:03 UTC
Parallelism
85
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,745,899
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x62be7533
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0x6a4a378e
#8
setData
#9
0x6c91e0…3e82
#10
0x568c4c…d676
#11
0xe0c908…056d
#12
withdraw
#2
executePacked
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
0x74fa2096…56ea
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…0001
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…00cc
0x25ef1a…5bf1
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
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