pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,290,688
← previous block
next block →
recent activity
Analyzing
Block #86,290,688
10 transactions · 9 stateful · 2026-07-07 23:25:07 UTC
Parallelism
70
/100
Blocked
56
%
Avg conflicts / tx
0.7
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,290,688
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 5
#7
updateDataFeedsValuesPartial
#8
setData
#3
execOrders
· blocks 1
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
5
w1
6
w2
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x7cddc117…5c3a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf796eaef…fac5
0x34b655…2a6f
4 touches
1 conflict
0x0654b954…7285
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
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
3 conflicts on slot
0xec0e022022…becb90
Audit this contract →
← previous block
·
next block →
recent activity