pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,046,044
← previous block
next block →
recent activity
Analyzing
Block #96,046,044
13 transactions · 12 stateful · 2026-08-14 23:16:23 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,046,044
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
execOrder
#4
execOrders
· blocks 1
#5
updateDataFeedsValuesPartial
#6
swap
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
updateDataFeedsValuesPartial
#11
0xed82b078
#12
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e92a8bd…fa3e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0008
0x28f627…d5fc
2 touches
0 conflicts
0x00000000…0009
0x28f627…d5fc
2 touches
0 conflicts
0x00000000…000a
0x28f627…d5fc
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x02693e83…54be
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
0x7e92a8bd8c…f3fa3e
Audit this contract →
← previous block
·
next block →
recent activity