pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,596,338
← previous block
next block →
recent activity
Analyzing
Block #85,596,338
8 transactions · 6 stateful · 2026-07-04 18:13:58 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,596,338
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
#4
execFwdPositionOps
· blocks 1
#6
0x6a494dde
#7
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xcf67cfe0…8995
0x34b655…2a6f
3 touches
1 conflict
0xb525d19a…26de
0x34b655…2a6f
3 touches
1 conflict
0x471fb752…394e
0x34b655…2a6f
2 touches
0 conflicts
0x69f27cf1…3797
0x34b655…2a6f
2 touches
0 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
2 touches
0 conflicts
0x810a3aa2…0227
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:
Perpl
1 conflict on slot
0xafd867b7ed…d92b2e
Audit this contract →
← previous block
·
next block →
recent activity