pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,786,329
← previous block
next block →
recent activity
Analyzing
Block #85,786,329
11 transactions · 8 stateful · 2026-07-05 15:20:14 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,786,329
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x303725…3058
#10
0x39435dac
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89750670…2dea
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x06bbc3af…6b3f
0xa6afd3…d132
4 touches
1 conflict
0x611f7aea…b097
0xa6afd3…d132
3 touches
1 conflict
0xd3eb4a53…fb87
0xa6afd3…d132
3 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x5cc231f5…f1cd
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x89750670de…b02dea
Audit this contract →
← previous block
·
next block →
recent activity