pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,022,520
← previous block
next block →
recent activity
Analyzing
Block #96,022,520
10 transactions · 9 stateful · 2026-08-14 21:18:01 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,022,520
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
execFwdPositionOpsV2
#4
0x94defb17
· blocks 1
#6
execFwdPositionOpsV2
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7090389…c321
0x968279…9342
4 touches
1 conflict
0xb7090389…c322
0x968279…9342
4 touches
1 conflict
0xb7090389…c325
0x968279…9342
4 touches
1 conflict
0xb7090389…c326
0x968279…9342
4 touches
1 conflict
0xb7090389…c328
0x968279…9342
4 touches
1 conflict
0xdcb3892e…a96a
0x968279…9342
4 touches
1 conflict
0xdcb3892e…a96b
0x968279…9342
4 touches
1 conflict
0xdcb3892e…a96d
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0xb709038922…2cc321
Audit this contract →
← previous block
·
next block →
recent activity