pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,320,858
← previous block
next block →
recent activity
Analyzing
Block #99,320,858
9 transactions · 9 stateful · 2026-08-26 11:47:40 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,320,858
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execFwdPositionOpsV2
· blocks 1
#3
execFwdPositionOpsV2
#4
0x3f5c179b
#5
batchUpdate
#7
0xed82b078
#8
setData
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x6a58ad35…d96b
0x34b655…2a6f
4 touches
1 conflict
0xfe65bb7b…12d7
0x34b655…2a6f
4 touches
1 conflict
0x28ca2678…af4d
0x34b655…2a6f
4 touches
1 conflict
0x25191452…d2ed
0x34b655…2a6f
2 touches
0 conflicts
0x26923160…9f8d
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f24
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
0x38bcfe5f82…986c71
Audit this contract →
← previous block
·
next block →
recent activity