pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,599,260
← previous block
next block →
recent activity
Analyzing
Block #96,599,260
9 transactions · 8 stateful · 2026-08-16 21:39:09 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,599,260
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
#3
0x3f5c179b
· blocks 1
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0af4a0c5…c070
0x34b655…2a6f
2 touches
0 conflicts
0x147a1e75…aefb
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x2a296f2d…2630
0x34b655…2a6f
2 touches
0 conflicts
0x3914dd1d…3d72
0x34b655…2a6f
2 touches
0 conflicts
0x39aa59ee…7b1f
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0xf219f7cff4…0f7379
Audit this contract →
← previous block
·
next block →
recent activity