pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,609,578
← previous block
next block →
recent activity
Analyzing
Block #96,609,578
11 transactions · 9 stateful · 2026-08-16 22:31:03 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,609,578
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
setData
#10
execOrders
#2
0x5acec890
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
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02c7fac9…a15f
0x34b655…2a6f
2 touches
0 conflicts
0x0a7a49dc…a295
0x34b655…2a6f
2 touches
0 conflicts
0x0b82a929…9a58
0x34b655…2a6f
2 touches
0 conflicts
0x0e7a1107…bf62
0x34b655…2a6f
2 touches
0 conflicts
0x1907196e…8745
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity