pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,605,633
← previous block
next block →
recent activity
Analyzing
Block #98,605,633
13 transactions · 11 stateful · 2026-08-23 23:26:08 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,605,633
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
exactInputSingle
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
updatePosition
#7
0x57368ddf
#9
transfer
· blocks 1
#11
setData
#12
execOrders
#8
execFwdPositionOpsV2
#10
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24bb46f7…3853
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x4e12117e…d2cf
0x34b655…2a6f
2 touches
0 conflicts
0x50c61506…343f
0x34b655…2a6f
2 touches
0 conflicts
0x70986451…c6bd
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
0xa11b60f7c7…f88e8b
Audit this contract →
← previous block
·
next block →
recent activity