pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,249,077
← previous block
next block →
recent activity
Analyzing
Block #85,249,077
11 transactions · 9 stateful · 2026-07-03 03:41:24 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,249,077
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#5
execOrders
#6
0x6a472fdc
#7
setData
#8
redeem
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0x6f64c012…6358
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
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
0xcdc1731c6b…b6b91a
Audit this contract →
← previous block
·
next block →
recent activity