pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,761,717
← previous block
next block →
recent activity
Analyzing
Block #85,761,717
11 transactions · 11 stateful · 2026-07-05 12:36:20 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,761,717
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
updateTemporalNumericValuesV1
#6
updateDataFeedsValuesPartial
#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
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x076e4b80…4d01
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0xe5cc87e8…0b27
0x34b655…2a6f
4 touches
1 conflict
0xfadc00f2…fb6e
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity