pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,629,977
← previous block
next block →
recent activity
Analyzing
Block #86,629,977
11 transactions · 9 stateful · 2026-07-09 13:13:56 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,629,977
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
0x3f5c179b
#5
execFwdPositionOps
#7
setData
#8
0xb8024e54
#9
execOrders
#10
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0a7bbfd8…ebde
0x34b655…2a6f
2 touches
0 conflicts
0x16be067e…1565
0x34b655…2a6f
2 touches
0 conflicts
0x3aeb946d…ff76
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4c43f8d0…6910
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
0xa7013be2a1…9ac0a8
Audit this contract →
← previous block
·
next block →
recent activity