pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,825,347
← previous block
next block →
recent activity
Analyzing
Block #85,825,347
10 transactions · 9 stateful · 2026-07-05 19:40:04 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,825,347
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
execFwdPositionOps
#6
handleOps
· blocks 1
#8
0x6a4ab38c
#9
setData
#7
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73cb5554…4902
0x754704…b603
4 touches
1 conflict
0x00000000…0005
0x62ab75…c800
4 touches
1 conflict
0x5818f8a8…3620
0x62ab75…c800
4 touches
1 conflict
0x5818f8a8…3622
0x62ab75…c800
4 touches
1 conflict
0x5818f8a8…3628
0x62ab75…c800
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
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:
USDC (USDC)
1 conflict on slot
0x73cb5554dd…ee4902
Audit this contract →
← previous block
·
next block →
recent activity