pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,363,944
← previous block
next block →
recent activity
Analyzing
Block #86,363,944
12 transactions · 9 stateful · 2026-07-08 07:34:17 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,363,944
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
execFwdPositionOps
#6
batchUpdate
#7
setData
#8
0x058b59…4aa8
#9
execOrders
· blocks 1
#11
0xc7e3ec2c
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64461c10…e86d
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5dc93134…aaef
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x29fae93a…bc42
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
0x64461c10d4…d1e86d
Audit this contract →
← previous block
·
next block →
recent activity