pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,528,528
← previous block
next block →
recent activity
Analyzing
Block #98,528,528
13 transactions · 10 stateful · 2026-08-23 16:44:04 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,528,528
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
exactInputSingle
#7
0x9e76c652
#8
execFwdPositionOpsV2
#9
setData
#10
approve
#11
execOrders
#12
execOrders
#2
0x9025acd4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eda77ad…d9bb
0x6285ac…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x00c33f26…b59c
0x2ab50b…5c41
2 touches
0 conflicts
0x00edc3bf…6c37
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x0ffd9cbf…f9c5
0x2ab50b…5c41
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:
0x6285ac23…757777
1 conflict on slot
0x9eda77addf…54d9bb
Audit this contract →
← previous block
·
next block →
recent activity