pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,449,089
← previous block
next block →
recent activity
Analyzing
Block #98,449,089
13 transactions · 9 stateful · 2026-08-23 09:58:25 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,449,089
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0x320c0058
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
approve
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#12
execute
#2
matchOrders
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
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x25d5e04e…3ef4
0x754704…b603
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
2 touches
0 conflicts
0x0be747d5…22e1
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
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:
USDC (USDC)
1 conflict on slot
0x64b004aba0…1660af
Audit this contract →
← previous block
·
next block →
recent activity