pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,542,398
← previous block
next block →
recent activity
Analyzing
Block #96,542,398
9 transactions · 8 stateful · 2026-08-16 16:53:09 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,542,398
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#4
updateDataFeedsValuesPartial
#6
forward
#7
setData
#8
execute
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0xeb7c08af…2105
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x007ee8e5…790b
0x34b655…2a6f
2 touches
0 conflicts
0x13c59388…47cb
0x34b655…2a6f
2 touches
0 conflicts
0x272273e3…7915
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x3f78072a…d0be
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
0xbdc80bf733…aae947
Audit this contract →
← previous block
·
next block →
recent activity