pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,438,536
← previous block
next block →
recent activity
Analyzing
Block #96,438,536
11 transactions · 10 stateful · 2026-08-16 08:10:26 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,438,536
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
0x94defb17
· blocks 1
#7
updateTemporalNumericValuesV1
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#5
0x94defb17
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x918c87a1…4e6b
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x8ca091ac…2250
0x968279…9342
4 touches
1 conflict
0x8ca091ac…2251
0x968279…9342
4 touches
1 conflict
0x8ca091ac…2254
0x968279…9342
4 touches
1 conflict
0x8ca091ac…2255
0x968279…9342
4 touches
1 conflict
0x8ca091ac…2257
0x968279…9342
4 touches
1 conflict
0x918c87a1…4e68
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
0x918c87a1ba…894e6b
Audit this contract →
← previous block
·
next block →
recent activity