pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,532,006
← previous block
next block →
recent activity
Analyzing
Block #96,532,006
9 transactions · 7 stateful · 2026-08-16 16:00:53 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,532,006
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcee216…2eb2
#2
0x325dd70c
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
· blocks 1
#8
setData
#5
dagSwapByOrderId
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x00000000…0003
0x850662…52d0
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
0x00000000…0005
0x850662…52d0
4 touches
1 conflict
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:
0x0a332311…6e0a3c
1 conflict on slot
0xb1632c2f29…54d991
Audit this contract →
← previous block
·
next block →
recent activity