pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,131,023
← previous block
next block →
recent activity
Analyzing
Block #96,131,023
35 transactions · 22 stateful · 2026-08-15 06:23:46 UTC
Parallelism
86
/100
Blocked
50
%
Avg conflicts / tx
0.51
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,131,023
· 35 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x0c7abd22
#3
0x0c7abd22
#4
0x0c7abd22
#5
0x0c7abd22
#7
execute_route
#9
0x1094dc9f
#10
0x775c78…3972
#11
0x00891485
#12
0x05ee6a22
#13
0x6c05cd2b
#14
execOrder
· blocks 3
#17
0x5acec890
· blocks 1
#19
0x5acec890
#20
updateDataFeedsValuesPartial
#21
updateDataFeedsValuesPartial
#22
execFwdPositionOpsV2
· blocks 3
#24
execFwdPositionOpsV2
#25
setData
· blocks 1
#27
0x3f5c179b
#30
0xed82b078
· blocks 1
#33
updateTemporalNumericValuesV1
#34
0x2378dc…1d37
#6
0x0c7abd22
· blocks 1
#15
execOrder
· blocks 1
#16
execOrder
#23
execFwdPositionOpsV2
· blocks 3
#26
setData
#31
0xed82b078
#8
0x4f819052
#18
0x5acec890
#28
execFwdPositionOpsV2
· blocks 2
#29
execFwdPositionOpsV2
· blocks 1
#32
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
8
w2
14
w0
15
w1
16
w1
17
w0
18
w2
22
w0
23
w1
25
w0
26
w1
28
w2
29
w3
30
w0
31
w1
32
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1450f862…235e
0x34b655…2a6f
6 touches
3 conflicts
0x0728ec77…146c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
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:
Perpl
6 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity