pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,308,041
← previous block
next block →
recent activity
Analyzing
Block #99,308,041
11 transactions · 9 stateful · 2026-08-26 10:43:12 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,308,041
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execPerpOps
#4
exactInputSingle
#5
execFwdPositionOpsV2
· blocks 1
#7
0x6a8ec3b7
#8
setData
#9
execOrders
#6
execFwdPositionOpsV2
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa77dd907…4cb5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd814f518…f5b4
0x34b655…2a6f
4 touches
1 conflict
0xd9722304…6ed0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
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
0xa77dd9071a…d34cb5
Audit this contract →
← previous block
·
next block →
recent activity