pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,532,113
← previous block
next block →
recent activity
Analyzing
Block #96,532,113
14 transactions · 10 stateful · 2026-08-16 16:01:25 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,532,113
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xf18489…4f0a
#3
0x0fb999…d97c
#4
0x5acec890
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
0x0c7abd22
#9
forward
#10
transfer
· blocks 1
#12
setData
#13
0x990df4…28f4
#11
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x16839256…371f
0x34b655…2a6f
2 touches
0 conflicts
0x1a5d321d…a474
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
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
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity