pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,697,179
← previous block
next block →
recent activity
Analyzing
Block #96,697,179
12 transactions · 9 stateful · 2026-08-17 05:51:37 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,697,179
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#5
0x57368ddf
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
transfer
#10
setData
#11
execOrders
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1294a92c…f91e
0x34b655…2a6f
4 touches
1 conflict
0x3f2796bf…f0fa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2dd03fb9…6243
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6571
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6572
0x34b655…2a6f
2 touches
0 conflicts
0x5c10927c…58e5
0x34b655…2a6f
2 touches
0 conflicts
0x5df7cf2b…bbe5
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
0x1294a92cb3…c5f91e
Audit this contract →
← previous block
·
next block →
recent activity