pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,667,578
← previous block
next block →
recent activity
Analyzing
Block #85,667,578
11 transactions · 9 stateful · 2026-07-05 02:08:13 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.45
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,667,578
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
exactInputSingle
#5
execFwdPositionOps
· blocks 2
#6
0x3f5c179b
#7
setData
#8
execOrders
· blocks 2
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
9
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab3ba25f…ec78
0x34b655…2a6f
6 touches
3 conflicts
0x505d32fe…14ad
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0xb4bc16a4…4825
0x34b655…2a6f
4 touches
1 conflict
0xe612dd74…eeec
0x34b655…2a6f
4 touches
1 conflict
0x83dee4ed…fbad
0x34b655…2a6f
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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
3 conflicts on slot
0xab3ba25fbd…22ec78
Audit this contract →
← previous block
·
next block →
recent activity