pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,409,657
← previous block
next block →
recent activity
Analyzing
Block #87,409,657
13 transactions · 10 stateful · 2026-07-13 04:06:45 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,409,657
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execPerpOps
#4
execPerpOps
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
#10
execFwdPositionOps
#11
setData
#12
execOrders
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22af2208…099e
0x34b655…2a6f
4 touches
1 conflict
0x274ac476…27fa
0x34b655…2a6f
4 touches
1 conflict
0x00842ba8…bdc6
0x34b655…2a6f
4 touches
1 conflict
0x6638e124…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x80bf58f2…be95
0x34b655…2a6f
4 touches
1 conflict
0x80bf58f2…be96
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
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
0x22af2208f2…fe099e
Audit this contract →
← previous block
·
next block →
recent activity