pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,532,163
← previous block
next block →
recent activity
Analyzing
Block #96,532,163
10 transactions · 10 stateful · 2026-08-16 16:01:40 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,532,163
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
claim
#2
0x5acec890
#3
0x5acec890
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x31e052ed…3133
0x386489…7508
2 touches
0 conflicts
0x57cad707…29d8
0x386489…7508
2 touches
0 conflicts
0xa87811b6…3d87
0x3ef3d8…d9ae
2 touches
0 conflicts
0xa87811b6…3d88
0x3ef3d8…d9ae
2 touches
0 conflicts
0xc264ec0f…58e4
0x3ef3d8…d9ae
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity