pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,818,734
← previous block
next block →
recent activity
Analyzing
Block #86,818,734
11 transactions · 10 stateful · 2026-07-10 10:15:53 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,818,734
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
· blocks 1
#3
execFwdPositionOps
#4
verifyOracleProofV2
#5
0x3b073534
#6
execFwdPositionOps
#7
0x6a50c6d1
#8
setData
#9
execOrders
· blocks 1
#2
execPerpOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9f45
0x16f70c…c3dd
2 touches
0 conflicts
0x71aeb674…e96f
0x34b655…2a6f
2 touches
0 conflicts
0x7b6c252d…a696
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity