pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,670,389
← previous block
next block →
recent activity
Analyzing
Block #85,670,389
8 transactions · 7 stateful · 2026-07-05 02:26:55 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,670,389
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
redeemDelegations
#4
setData
#5
execOrders
· blocks 1
#7
0xc7e3ec2c
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x0cb4073f…4730
0x34b655…2a6f
2 touches
0 conflicts
0x24f9b85d…b7b7
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…caca
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
0x1aaf499609…4665ec
Audit this contract →
← previous block
·
next block →
recent activity