pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,193,062
← previous block
next block →
recent activity
Analyzing
Block #86,193,062
9 transactions · 8 stateful · 2026-07-07 12:33:18 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,193,062
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
withdraw
#2
0x6ad2e98b
#3
updatePrices
#4
execOrders
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#5
execOrders
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xfb6cac17…e732
0x34b655…2a6f
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0008
0x7821ba…01d0
2 touches
0 conflicts
0x00000000…000b
0x7821ba…01d0
2 touches
0 conflicts
0x00000000…000c
0x7821ba…01d0
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
0x1b5d2e607a…9999b5
Audit this contract →
← previous block
·
next block →
recent activity