pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,166,728
← previous block
next block →
recent activity
Analyzing
Block #85,166,728
10 transactions · 10 stateful · 2026-07-02 18:32:53 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,166,728
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setAddressWhitelisted
#5
execFwdPositionOps
#6
setData
#7
execOrders
· blocks 1
#9
0xc7e3ec2c
#2
0x5a5d9a99
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23778a1f…dec4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x85ca9064…f72f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec1d7176…6f5e
0x34b655…2a6f
4 touches
1 conflict
0x207d2870…e720
0x34b655…2a6f
2 touches
0 conflicts
0x2380625c…1123
0x34b655…2a6f
2 touches
0 conflicts
0x2ed98d3b…78ef
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
0x23778a1fe7…dfdec4
Audit this contract →
← previous block
·
next block →
recent activity