pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,323,593
← previous block
next block →
recent activity
Analyzing
Block #86,323,593
12 transactions · 10 stateful · 2026-07-08 03:05:01 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,323,593
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
approve
#4
execOrders
· blocks 1
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
· blocks 1
#8
execFwdPositionOps
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x9609077c…b811
0x34b655…2a6f
4 touches
1 conflict
0xb3c96942…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0xa1830b71…6cd6
0x34b655…2a6f
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
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:
Perpl
1 conflict on slot
0x4bfdcd5135…769b58
Audit this contract →
← previous block
·
next block →
recent activity