pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,582,189
← previous block
next block →
recent activity
Analyzing
Block #85,582,189
11 transactions · 10 stateful · 2026-07-04 16:39:42 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,582,189
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePosition
#3
execFwdPositionOps
· blocks 1
#4
verifyOracleProofV2
#5
forward
#6
0x6a4937c6
#7
setData
#10
execOrders
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x0d22d8bd…b7b4
0x6657d1…8ccc
2 touches
0 conflicts
0x138d2142…59f1
0x6657d1…8ccc
2 touches
0 conflicts
0x304e0c27…a224
0x6657d1…8ccc
2 touches
0 conflicts
0x3fdad214…76d4
0x6657d1…8ccc
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
0xefcdf19725…1096a2
Audit this contract →
← previous block
·
next block →
recent activity