pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,601,313
← previous block
next block →
recent activity
Analyzing
Block #96,601,313
13 transactions · 10 stateful · 2026-08-16 21:49:28 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,601,313
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updatePrices
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
· blocks 1
#8
transferWithAuthorization
#9
transfer
#10
setData
#11
execOrders
#12
0x3a6300…a634
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x16e75abd…f3ad
0x34b655…2a6f
2 touches
0 conflicts
0x1e141255…5aec
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbed17…4f3b
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbed17…4f3c
0x34b655…2a6f
2 touches
0 conflicts
0x239faba0…555b
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
0x5615326245…a221ce
Audit this contract →
← previous block
·
next block →
recent activity