pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,536,668
← previous block
next block →
recent activity
Analyzing
Block #98,536,668
10 transactions · 10 stateful · 2026-08-23 17:26:24 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,536,668
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0xab083028
#4
execOrders
#5
0x59558d29
#6
verifyOracleProofV2
#7
execFwdPositionOpsV2
· blocks 1
#8
redeemDelegations
#9
execOrders
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
0xebcb0f2d…9305
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x062fa9cf…b1f1
0x34b655…2a6f
2 touches
0 conflicts
0x1408e7c7…f324
0x34b655…2a6f
2 touches
0 conflicts
0x141def99…ea38
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
0xebcb0f2dca…da9305
Audit this contract →
← previous block
·
next block →
recent activity