pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,630,773
← previous block
next block →
recent activity
Analyzing
Block #86,630,773
12 transactions · 11 stateful · 2026-07-09 13:19:16 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,630,773
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
removeLiquidityNATIVE
#2
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#4
settle
#6
0x6a4fa04b
#7
0x3e51b7…de2b
#8
setData
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#5
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x87ee379a…cd9e
0x34b655…2a6f
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x899e99ab…504b
0x5afd3e…7620
2 touches
0 conflicts
0xc3b4e393…2a34
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity