pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,096,162
← previous block
next block →
recent activity
Analyzing
Block #99,096,162
12 transactions · 10 stateful · 2026-08-25 16:57:05 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,096,162
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
#2
execOrders
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
0xed82b078
#10
0x6a8dc9d8
#11
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd173f390…84de
0x34b655…2a6f
4 touches
1 conflict
0x2b69cc9b…2aca
0x34b655…2a6f
4 touches
1 conflict
0x42cb53d6…7017
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x757dd9d2…0fb5
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0000
0x2b37ef…0bdc
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
0xd173f39088…dc84de
Audit this contract →
← previous block
·
next block →
recent activity