pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,483,299
← previous block
next block →
recent activity
Analyzing
Block #86,483,299
12 transactions · 9 stateful · 2026-07-08 20:52:18 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,483,299
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6d2de3…09d8
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0x39abec6b
#7
0xed82b078
#8
0x6a4eb8f9
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02956ce9…f576
0x2ab50b…5c41
2 touches
0 conflicts
0x09a8bb29…b290
0x2ab50b…5c41
2 touches
0 conflicts
0x15a8b5e6…0296
0x2ab50b…5c41
2 touches
0 conflicts
0x21a005d7…c779
0x2ab50b…5c41
2 touches
0 conflicts
0x268837a0…1ccf
0x2ab50b…5c41
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
0x0ab54c30a6…82b88e
Audit this contract →
← previous block
·
next block →
recent activity