pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,875,870
← previous block
next block →
recent activity
Analyzing
Block #99,875,870
12 transactions · 11 stateful · 2026-08-28 10:34:55 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,875,870
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#7
execPerpOps
#8
execPerpOps
#9
setData
#10
execFwdPositionOpsV2
#11
0x3f5c179b
#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
0x00532bf5…5711
0x754704…b603
4 touches
1 conflict
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0x777c9106…162a
0x754704…b603
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
2 touches
0 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
2 touches
0 conflicts
0xecd87a39…d9c5
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
0x00532bf5f9…035711
Audit this contract →
← previous block
·
next block →
recent activity